hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.9 Service discovery and selection | The Service discovery and selection function is an application of a DVB-HB Client with the task of compiling a local copy of the Service List, collecting Content Guide metadata and controlling the Content playback function. In case of Profile A, Service List(s) and Content Guide data may be retrieved over the M reference point or, in alternative, may be compiled by the Service discovery and selection function by means of a frequency scan, performed via remote tuning commands generated by the Content playback function according to the indications sent over the CU_A reference point. In case of Profile B, Service List(s) and Content Guide data are retrieved over the M reference point according to ETSI TS 103 770 [3]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.10 Resource availability map function | The Resource availability map function is an optional function with the task of exposing the static capabilities of the device (e.g. number and type of tuners) and the instantaneous resources availability in order to efficiently allow sharing the resources among multiple DVB-HB Clients. The function includes a Device capabilities & availability map subfunction generating the data to be exposed as XML documents and a Web server subfunction for publication (HTTP(S) server). To achieve its tasks, the Resource availability map function relies on information generated by the Service List publication function and its subfunctions. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 24 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11 Content playback | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.1 General description | The Content playback function is the entity in the DVB-HB Client managing request, reception and presentation of content. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.2 Content playback function for Profile A | In case of Profile A, request and reception of the selected service are managed by the SAT>IP client subfunction. It interacts with the Content publication function of the DVB-HB Local Server by sending requests over the CL_A reference point and retrieving the requested content over the L_A reference point according to the protocols defined in EN 50585 [1]. Optionally, additional AL-FEC packets associated with the data packets are received over the L_A reference point by the Network resilience (Rx) subfunction for error correction, as defined in clause 8.4.2. The Content consumption (TS) subfunction manages presentation of content in TS format for consumption by the user. As browser-based (HTML5+Javascript) players do not support HTTP-based video streaming, a dedicated application is used. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.3 Content playback function for Profile B | In case of Profile B, request and reception of the selected service are managed by the DVB-DASH client subfunction. It sends HTTP(S) requests to the Origin server subfunction of the DVB-HB Local Server over the CL_B reference point, retrieving the requested content over the L_B reference point as defined in ETSI TS 103 285 [2]. The Content consumption (DASH) subfunction manages presentation of content formatted as defined in ETSI TS 103 285 [2] for consumption by the user. The audio/video player may be implemented in a browser (HTML5+Javascript) or as a dedicated application. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.12 External repository | This is an external function, out of scope of the present document. It represents an external repository (e.g. a remote server, a Universal Serial Bus (USB) memory stick, etc.) of service list metadata, accessed by the Service List publication function via the proprietary reference point E in alternative to generating them locally on the basis of the DVB-SI metadata received over the T reference point. How the service list is produced in this case is out of scope of the present document. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6 DVB-HB Local Server announcement and discovery | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.1 Introduction | In Profile A, in order to ensure backwards compatibility with existing devices supporting EN 50585 [1], the DVB-HB Local Server Announcement and DVB-HB Local Server discovery functions are implemented using a simplified version of Universal Plug and Play (UPnP) according to ISO/IEC 29341-1-1 [13]. In Profile B, the main method for DVB-HB Local Server Announcement and DVB-HB Local Server discovery is based on Multicast Domain Name System (mDNS) and Domain Name System - Service Discovery (DNS-SD). However, since Profile B aims to support also browser-based DVB-HB Clients, such method is not applicable in all the use-cases. In fact, discovery mechanisms based on UPnP or mDNS rely on UDP multicast packet transmission, a type of transmission that cannot be supported natively by HTML5+Javascript clients. It is recognized that this issue does not affect all the implementation scenarios that can be foreseen for Profile B DVB-HB Clients. For instance, an exemplary (non-exhaustive) list is given below: • DVB-HB Client App installed on the user terminal. In this case, not being browser-based, there are no specific constraints on the mechanism adopted. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 25 • Browser-based standard DVB-I Client hosted on a well-known web site (e.g. the DVB Internet (DVB-I) reference client). In this case automatic discovery is not applicable, and the IP address of the service list exposed by DVB-HB Local Server has to be provided manually. • Browser-based DVB-HB Client hosted by the DVB-HB Local Server itself. In this case, two options are possible either the DVB-HB Local Server also provides a discovery mechanism based on UPnP as described in clause 6.3.2, or automatic discovery is not applicable as, for the first time at least, user has to type the DVB-HB Local Server's address in the browser. The DVB-HB Client may automatically discover additional DVB-HB Local Servers present on the same LAN. • Browser-based DVB-HB Client hosted on a well-known web site. In this case automatic discovery is applicable, however a solution based on UPnP cannot be used. In order to cover all of the possible alternatives, besides the mandatory method based on mDNS, few additional optional mechanisms for Profile B DVB-HB Local Server discovery are outlined in the present clause, as well as other informative implementation-specific guidelines. NOTE: While not natively supported by browser-based (HTML5+Javascript) DVB-HB Client, mDNS may be supported by a browser plug-in, binding a port in the system listening to multicast messages. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.2 Profile A DVB-HB Local Server discovery | Profile A DVB-HB Local Server announcement and discovery shall be implemented according to EN 50585 [1]. The mechanism relies on the Simple Service Description Protocol (SSDP) as specified in ISO/IEC 29341-1-1 [13]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3 Profile B DVB-HB Local Server discovery | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.1 Introduction | Profile B DVB-HB Local Server announcement and discovery shall be implemented according to mDNS and DNS-SD, as described in clause 6.3.5. Additionally, a Profile B DVB-HB Local Server may implement one or more of the discovery mechanisms described in clause 6.3.2, clause 6.3.3 and clause 6.3.4. Different implementations of Profile B DVB-HB Clients may take advantage of one or the other of such mechanisms. Manual input of the DVB-HB Local Server's IP address within the client can always be implemented as a fallback solution. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.2 Optional discovery mechanism based on UPnP | When targeting clients capable of UPnP-based discovery, a Profile B DVB-HB Local Server implementing this method shall announce its presence on the LAN according to EN 50585 [1], with the differences indicated below. The mechanism relies on the SSDP as specified in ISO/IEC 29341-1-1 [13]. With respect to EN 50585 [1], the following differences apply: • The device type, or Uniform Resource Name (URN), shall be set to: urn:dvb:metadata:device:HBLocalServer:1 • The XML document referenced by the LOCATION field in the headers of the multicast NOTIFY ssdp:alive messages shall include an additional <dvbhb:X_ServiceListEntryPoints> capabilities element providing the URL of the Service List Entry Points exposed by the DVB-HB Local Server (see also clause 7). • If the DVB-HB Local Server integrates an HTTP server with an end-user interface (e.g. providing HTML5+Javascript code of a DVB-HB Client), the URL to the presentation root should be provided in the <presentationURL> element of the XML document referenced by the LOCATION field. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 26 NOTE: According to ISO/IEC 29341-1-1 [13], such presentation URL is relative to the URL at which the device description is located. Pseudocode 1 shows an example of SSDP packets when a DVB-HB Local Server implementing UPnP announces its presence on the LAN, while pseudocode 2 shows an example of the XML document referenced by the LOCATION field. Pseudocode 1: Example of announcement of a DVB-HB Local Server based on UPnP NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=1800 LOCATION: http://10.54.128.122:8088/dvbhb_server.xml NT: upnp:rootdevice NTS: ssdp:alive SERVER: Linux/1.0 UPnP/1.1 IDL4K/1.0 USN: uuid:6b9695fe-813f-11ed-a1eb-0242ac120002::upnp:rootdevice BOOTID.UPNP.ORG: 2318 CONFIGID.UPNP.ORG: 0 DEVICEID.SES.COM: 1 NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=1800 LOCATION: http://10.54.128.122:8088/dvbhb_server.xml NT: uuid:6b9695fe-813f-11ed-a1eb-0242ac120002 NTS: ssdp:alive SERVER: Linux/1.0 UPnP/1.1 IDL4K/1.0 USN: uuid:6b9695fe-813f-11ed-a1eb-0242ac120002 BOOTID.UPNP.ORG: 2318 CONFIGID.UPNP.ORG: 0 DEVICEID.SES.COM: 1 NOTIFY * HTTP/1.1 HOST: 239.255.255.250:1900 CACHE-CONTROL: max-age=1800 LOCATION: http://10.54.128.122:8088/dvbhb_server.xml NT: urn:dvb:metadata:device:HBLocalServer:1 NTS: ssdp:alive SERVER: Linux/1.0 UPnP/1.1 IDL4K/1.0 USN: uuid:6b9695fe-813f-11ed-a1eb-0242ac120002::urn:dvb.metadata:device:HBLocalServer:1 BOOTID.UPNP.ORG: 2318 CONFIGID.UPNP.ORG: 0 DEVICEID.SES.COM: 1 Pseudocode 2: Example of UPnP device description XML document exposed by a Profile B DVB-HB Local Server <?xml version="1.0"?> <root xmlns="urn:schemas-upnp-org:device-1-0" configId="1"> <specVersion> <major>1</major> <minor>1</minor> </specVersion> <device> <deviceType>urn:dvb:metadata:device:HBLocalServer:1</deviceType> <friendlyName>DVB-HB Profile B Local Server</friendlyName> <manufacturer>DVB-HB Local Server Manufacturer</manufacturer> <manufacturerURL>http://www.dvbhb-localserver-manufacturer.com</manufacturerURL> <modelDescription>DVB-HB Profile B Local Server supporting UPnP</modelDescription> <modelName>DVB-HB Local Server</modelName> <serialNumber>HB-0242ac120002</serialNumber> <UDN>uuid:6b9695fe-813f-11ed-a1eb-0242ac120002</UDN> <iconList> <icon> <mimetype>image/png</mimetype> <width>64</width> <height>64</height> <depth>24</depth> <url>/icon.png</url> </icon> </iconList> <presentationURL>/index.html</presentationURL> <dvbhb:X_ServiceListEntryPoints xmlns:dvbhb="urn:dvb:metadata:dvbhb">/ServiceListEntryPoints.xml </dvbhb:X_ServiceListEntryPoints> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 27 </device> </root> |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.3 Optional discovery mechanism based on HTTP | When targeting clients capable of port-scanning a selected subnet, a Profile B DVB-HB Local Server implementing this method shall announce its presence on the LAN by exposing its Service List Entry Points on Transmission Control Protocol (TCP) port 61 277 (HTTP). During the discovery phase, DVB-HB Clients may scan the local subnet, looking for DVB-HB Local Servers active on that port. NOTE: The current discovery mechanism requires a-priori knowledge of the local subnet addressing details. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.4 Additional implementation-specific mechanisms | In addition to the optional discovery mechanisms specified above, other implementation-specific mechanisms supporting browser-based clients may be used. In this informative clause, two specific mechanisms are considered since they are closely related to similar solutions adopted in the present document or in other DVB specifications. User login via remote server When a remote server is available for client's authentication, this mechanism uses it as a middle node to connect a browser-based DVB-HB Client to a DVB-HB Local Server using the device unique identifier and user credentials associated with it. After logging into the remote server with the associated credentials, the client retrieves the relevant discovery information related to the user's DVB-HB Local Server(s), allowing it to retrieve the DVB-HB Local Server's local IP address. NOTE 1: This procedure may be done during the first installation, in background or each time the user starts the DVB-HB Client application, depending on the implementation. Device pairing When the DVB-HB Local Server has a display (e.g. it is connected to a monitor or TV screen) and the DVB-HB Client runs on a separate personal device (e.g. Personal Computer (PC), laptop, tablet, smartphone, etc.), the two devices can be paired using a selected "rendezvous" mechanism (e.g. alphanumeric code, QR code, URL, etc.). Once paired, the DVB-HB Local Server can send its IP address and capabilities to the DVB-HB Client, which can then start sending back the requests. NOTE 2: This procedure requires a remote server for the "rendezvous" mechanism. NOTE 3: The DVB-HB Local Server and DVB-HB Client may be paired during either the initial setup or at the beginning of a viewing session, depending on the implementation. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5 Discovery mechanism based on mDNS/DNS-SD | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.1 General | The method described in the present clause is intended to be applicable in DVB-HB and DVB-NIP [i.1] contexts. In particular, the term DVB Gateway indicates a device which may provide functions of a DVB-HB Local Server as defined in the present document, a DVB-NIP Gateway as defined in DVB Document A180 [i.1], or both. A DVB Gateway shall announce its presence on the LAN and answer DVB client host query requests using the DNS- SD mechanism defined in IETF RFC 6763 [14] in conjunction with mDNS as defined in IETF RFC 6762 [15] and according to the following: • A registered DVB Gateway service; • At least three Domain Name System (DNS) records: a Pointer (PTR) record, a Service (SRV) record and a Text (TXT) record. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 28 A client implementing this method shall support the DVB Gateway discovery according to IETF RFC 6763 [14] and IETF RFC 6762 [15], taking into account the information exposed in the DNS records as described in clause 6.3.5.2, clause 6.3.5.3 and clause 6.3.5.4. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.2 Pointer Record (PTR) | The PTR record is used to point clients looking for a DNS-SD service to the devices providing that service. The PTR record format is as follows: <Service Type>.<Domain> <TTL> PTR <Instance Name>.<Service Type>.<Domain> where: <Service Type> is the combination of a standard IP protocol name and a transport protocol name both prefixed with the underscore '_' character. The DVB Gateway shall use the following Service Type: _dvbservdsc._tcp. Additionally, the DVB Gateway should use the Service Type _http._tcp if the exposed service is also an HTTP server. <Domain> shall be set to local. <TTL> is the value in seconds of Time To Live in cache. <Instance Name> is the instance name of the service. It may be up to 63 bytes. Information on how to build Instance Names is provided in IETF RFC 6763 [14]. A recommendation is to provide short, descriptive and human-readable names. Unicode characters including spaces are allowed by IETF RFC 6763 [14]. Below are three examples of a DVB Gateway PTR record: _dvbservdsc._tcp.local. 86400 PTR DVB Gateway Manufacturer A Model B._dvbservdsc._tcp.local. _dvbservdsc._tcp.local. 86400 PTR Live TV Airport Lounge 2._dvbservdsc._tcp.local. _dvbservdsc._tcp.local. 86400 PTR dvb:gw:35:7B:12:48:DE:01._dvbservdsc._tcp.local. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.3 Service Record (SRV) | The SRV record has the following structure, as defined in IETF RFC 6763 [14] and IETF RFC 2782 [16]: <Instance Name>.<Service Type>.<Domain> <TTL> IN SRV <Priority> <Weight> <Transport Port> <IP addres s> It associates the name of a service (structured as <Instance Name>.<Service Type>.<Domain>) with the IP address and port number of a server (host device) that offers that service, allowing a client to discover the local DVB Gateway service. Below is an example of a DVB Gateway SRV record: DVB Gateway Model A._dvbservdsc._tcp.local. 86400 IN SRV 0 0 80 192.168.1.101. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.4 Text Record (TXT) | The TXT record is intended to convey a small amount of useful additional information about a service. It is a concatenated list of "key=value" pairs separated by semicolons, with the following structure: <Instance Name>.<Service Type>.<Domain> <TTL> TXT "<key_1>=<value_1>[;<key_n>=<value_n>]" Available keys for the TXT record are given in table 1. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 29 Table 1: TXT record keys Key Semantic Definition Constraints txtvers Decimal version number of the TXT record, as defined in IETF RFC 6763 [14]. Optional dvbi_sep URL of the Service List Entry Points exposed by the DVB Gateway according to clause 9.2. It can be local or remote. Either dvbi_sep or dvbi_sl is mandatory dvbi_sl URL of the DVB-I Service List exposed by the DVB Gateway. It can be local or remote. Either dvbi_sep or dvbi_sl is mandatory priv_loc URL of private signalling data for DVB Gateways not implementing DVB-I functionality. Optional cprot_ep URL pointing to content protection server. Optional manuf Manufacturer's name. Optional model Model name of the device. Optional sn Serial number of the device. Optional tuners List of pairs of supported modulation types and respective number of tuners. Multiple pairs are separated by " ". Modulation type and number of tuners of that kind are separated by "/". Possible values of modulation type are: "DVB-T", "DVB-T2", "DVB-S", "DVB-S2", "DVB-S2X", "DVB-C". Example: tuners=DVB-T2/4 DVB-S2/2 Optional orb_pos_A First received orbital position, expressed in positive or negative degrees representing East and West directions respectively. Relevant only if the DVB Gateway also includes satellite tuners. Optional orb_pos_B Second received orbital position, expressed in positive or negative degrees representing East and West directions respectively. Relevant only if the DVB Gateway also includes satellite tuners. Optional orb_pos_C Third received orbital position, expressed in positive or negative degrees representing East and West directions respectively. Relevant only if the DVB Gateway also includes satellite tuners. Optional orb_pos_D Fourth received orbital position, expressed in positive or negative degrees representing East and West directions respectively. Relevant only if the DVB Gateway also includes satellite tuners. Optional Optional parameters are intended for filtering at client-side in case several DVB Gateway are available on the LAN. However, according to IETF RFC 6763 [14], the TXT record is intended to be small, i.e. it should be kept below 1 300 bytes to fit into a single Ethernet packet. Information provided by omitted parameters can be retrieved via the extended Service List Entry Points XML document referenced by the dvbi_sep key. Below are two examples of a DVB Gateway TXT record. DVB Gateway Model A._dvbservdsc._tcp.local. 86400 IN TXT "txtvers=1;dvbi_sep=http://192.168.1.101:80 /ServiceListEntryPoints.xml" Live TV Airport Lounge 2._dvbservdsc._tcp.local. 86400 IN TXT "dvbi_sl=https://www.example.com/dvb- i/sl/Service-List_France_1.xml;tuners=DVB-S2/16;orb_pos_A=-5;orb_pos_B=19.2" |
98d566ac142ee06783f646c81587b072 | 104 025 | 7 Exposure of DVB-HB Local Server capabilities | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.1 Introduction | This clause defines how Profile A and Profile B DVB-HB Local Servers can announce their capabilities to DVB-HB Clients, including number and type of available tuners and encoding resources, together with any restrictions because of concurrent usage by other connected DVB-HB Clients. Clause 7.2 and clause 7.3 provide the detailed set of device capabilities and available resources announced by the DVB-HB Local Server. A Profile A DVB-HB Local Server shall expose basic information about itself in the form of an XML document (e.g. desc.xml) as defined in EN 50585 [1] and extended as defined in clause 8.3 of the present document. Such file is announced during the DVB-HB Local Server discovery phase (see clause 6). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 30 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 as defined in ETSI TS 103 770 [3], clause 5.3.2 and extended as defined in clause 9.2 of the present document. Such file is announced during the DVB-HB Local Server discovery phase (see clause 6). In both Profiles, the exposed information includes: • URL of the published DVB-I Service List (optional in Profile A, mandatory in Profile B). • Device description (i.e. brand, model, device identifier, supported version, etc.). • Device capabilities and resource availability map (optional). |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.2 Device capabilities | Capabilities of a DVB-HB Local Server are defined according to pseudocode 3, table 2 and table 3. HBLocalServerType replicates the same structure as defined by EN 50585 [1], aligned to UPnP syntax according to ISO/IEC 29341-1-1 [13], also for Profile B DVB-HB Local Servers. HBServiceAvailabilityType is used by both Profile A and Profile B DVB-HB Local Servers to announce their currently available resources. See also clause 8.3 and clause 9.2, respectively, for their use. Pseudocode 3: DVB-HB Local Server device capabilities schema <complexType name="HBxServiceListEntryPointsType" abstract="false"> <annotation> <documentation xml:lang="en"> DVB-HB extension to dvbi-types:ServiceListEntryPointsType </documentation> </annotation> <complexContent> <extension base="dvbi-types:ExtensionBaseType"> <sequence> <element name="HBLocalServerEntity" type="dvbhbx:HBLocalServerType" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType> <complexType name="HBLocalServerType"> <sequence> <element name="DeviceType" type="anyURI"/> <element name="UniqueDeviceName"> <simpleType> <restriction base="string"> <pattern value="uuid:[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}"/> </restriction> </simpleType> </element> <element name="UniversalProductCode" minOccurs="0"> <simpleType> <restriction base="string"> <pattern value="[0-9]{12}"/> </restriction> </simpleType> </element> <element name="ModelName" type="mpeg7:TextualType"/> <element name="FriendlyName" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="Manufacturer" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="ModelNumber" type="mpeg7:TextualType" minOccurs="0"/> <element name="SerialNumber" type="mpeg7:TextualType" minOccurs="0"/> <element name="ModelDescription" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/ > <element name="ManufacturerURL" type="anyURI" minOccurs="0"/> <element name="ModelURL" type="anyURI" minOccurs="0"/> <element name="Icon" type="tva:RelatedMaterialType" minOccurs="0" maxOccurs="unbounded"/> <element name="Availability" type="dvbhbx:HBServiceAvailabilityType" minOccurs="0"/> </sequence> <attribute name="specVersion" type="positiveInteger" use="required"/> </complexType> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 31 Table 2: HBLocalServerType fields Name Semantic Definition Constraints DeviceType Indicates the category of device, aligned to UPnP syntax. For a Profile B DVB-HB Local Server, it shall be set to urn:dvb:metadata:device:HBLocalServer:1. Mandatory UniqueDeviceName Universally-unique identifier for the device, whether root or embedded. It shall be the same over time for a specific device instance (i.e. it shall survive reboots). It shall be set to "uuid:" followed by a Universally Unique IDentifier (UUID) suffix specified by the vendor (the UUID string shall have the format specified in ISO/IEC 29341-1-1 [13]). Mandatory UniversalProductCode 12-digit, all-numeric code that identifies the consumer package. Managed by the Uniform Code Council. Specified by UPnP vendor. Optional 0 .. 1 ModelName Model name. Should be < 32 characters. Mandatory FriendlyName Short description for end user. Multiple values can be specified as long as they have different @xml:lang values. Should be < 64 characters. Mandatory 1 .. ∞ Manufacturer Manufacturer's name. Multiple values can be specified as long as they have different @xml:lang values. Should be < 64 characters. Mandatory 1 .. ∞ ModelNumber Model number. Should be < 32 characters. Optional SerialNumber Serial number of the device. Should be < 32 characters. Optional ModelDescription Long description for end user. Multiple values can be specified as long as they have different @xml:lang values. Should be < 128 characters. Mandatory 0 .. ∞ ManufacturerURL Web site for manufacturer. Optional ModelURL Web site for the model. Optional Icon Icon to depict device in a control point User Interface (UI). Optional 0 .. ∞ Availability Announces the capabilities of the DVB-HB Local Server in terms of type and number of front-ends (tuners). It also informs about real-time status in terms of used and available resources. See table 3 for semantic definition of HBServiceAvailabilityType. Optional 0 .. 1 @specVersion Defines the version on which the device is implemented. Mandatory Table 3: HBServiceAvailabilityType fields Name Semantic Definition Constraints OrbitalPosition Received orbital position(s) expressed in positive or negative degrees representing East and West directions respectively. Multiple occurrences are possible if multiple orbital positions are received. Relevant only if the DVB-HB Local Server also includes satellite tuners. Optional ServiceAvailabilityMapIdleURL URL of the ServiceAvailabilityMapIdle.xml document, which provides information on installed tuners and available services. Syntax of the ServiceAvailabilityMap.xml document is given in clause 7.3. Mandatory ServiceAvailabilityMapUpdateURL URL of the ServiceAvailabilityMapUpdate.xml document, which is used to update currently used resources in the ServiceAvailabilityMap with respect to ServiceAvailabilityMapIdle according to IETF RFC 5261 [17] (see also clause 7.3). Present if the DVB-HB Local Server supports resource sharing functionality. Optional 0 .. 1 @version Version of the ServiceAvailabilityMap exposed at URL ServiceAvailabilityMapIdleURL. The value shall be identical as inside the XML document and the same as in the DVB-I Service List. The version is incremented each time the files are updated, for example after an installation update or when the exposed DVB-I Service List is updated. DVB-HB Clients supporting resource sharing functionality can check the @version attribute and, if different from the previous one, download the new version of ServiceAvailabilityMapIdle.xml and ServiceAvailabilityMapUpdate.xml documents. Mandatory ETSI ETSI TS 104 025 V1.1.1 (2024-07) 32 |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3 Service Availability Map | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.1 Introduction | The effective availability of a service for a DVB-HB Client can be impacted by several limitations, including: • Unavailability of a frontend (tuner). • Unavailability of a sub-band, or polarization and sub-band, in case of Direct To Home (DTH) reception. • Processing limitations of a DVB-HB Local Server. • Bandwidth limitations of a DVB-HB Local Server. • Number of encoders (if transcoding is used). The capability of sharing DVB-HB Local Server resources among multiple DVB-HB Clients is an efficient way to increase the effective availability of services. Obviously, checking service availability is only relevant when there is lack of resources. In other words, if resources are overprovisioned, i.e. the available resources always allow all clients to be served with the requested services, then there is no need to efficiently manage resources or to analyse the actual usage by clients, as all services can simply offered at all times. The problem of sharing tuning resources is not new and is well known, for example in the context of STBs sharing a common Low Noise Block (LNB) feed (i.e. daisy chained LNB) or Personal Video Recorder (PVR) functionalities (i.e. watching one service while recording another one on the same or another multiplex). An additional challenge is the availability of transcoders. Moreover, use of resources by other clients is not known, because they are independent devices. For privacy reasons, a reporting of individual usage is not envisaged, but, fortunately, for assessing available services, only own usage (i.e. which resources would be freed before selecting a service) and a snapshot of what is used globally at server side is relevant - not the individual clients' usage. Since Profile A DVB-HB Clients request a specific encoding profile linked with the client request, it is assumed that, when a transcoded service is requested, it is on exclusive basis. Conversely, Profile B DVB-HB Clients can "share" transcoders for the same service. Although easier to define and handle, simply publishing the number of currently locked tuners would be insufficient, as the number of locked tuners does not permit to a DVB-HB Client to derive available services/resources, unless it assumes that all remaining tuners give access to all services. A simple list of available services provides more usable information, however the DVB-HB Client would not be able to consider what resources are released when switching to other services: the DVB-HB Client cannot assume that all services would be available, as some of the resources currently used may be shared with other clients, i.e. a release of such resource may not always lead to freeing it. The technical solution described in the following, under responsibility of the Resource Availability Map function (see clause 5.4.10), allows instead to cover the above cases. |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.2 Logical structure of the Service Availability Map | The comprehensive logical structure is organized in form of an XML document describing the dependencies among resource usage associated to each service. This is described in the file ServiceAvailabilityMap.xml, which is referred to in the device capabilities exposed by the DVB-HB Local Server (see clause 7.2). Logical structure and potential dependencies are represented in the hierarchy of the XML document. These dependencies are static, as they depend on the DVB-HB Local Server software functionality, hardware features and receiving antennas, while only the instantaneous usage of the resources changes. A DVB-HB Local Server implementing this feature shall keep an up-to-date Services Availability Map in accordance with its used resources. When accessing the ServiceAvaivabilityMap.xml document, the DVB-HB Client should be able to determine the available services and present them to the user on the UI. This proposal is applicable to both Profile A and Profile B DVB-HB Local Servers and DVB-HB Clients. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 33 The DVB-HB Local Server may internally use the ServiceAvailabilityMap.xml to manage its resources together with the information on DVB-HB Clients potentially releasing a resource. |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.3 ServiceAvailabilityMap.xml document | The ServiceAvailabilityMap.xml document is structured in a hierarchy of <DependencyResourceGroup> elements. All child <DependencyResourceGroup> elements are dependent to each other, i.e. if one of these child elements is in use by a DVB-HB Client, it limits usage of other child elements belonging to the same parent <DependencyResourceGroup> element (if a limit is set). If any of the child elements is used, then the parent <DependencyResourceGroup> element becomes used. EXAMPLE: In a typical case, the parent <DependencyResourceGroup> element could be a tuner, while its child <DependencyResourceGroup> elements could be the receivable multiplexes, each of them carrying a set of services. When one of the services in a multiplex is selected by a DVB-HB Client, the child <DependencyResourceGroup> element becomes 'used', and so also the parent <DependencyResourceGroup> element becomes 'used'. This means that other DVB-HB Clients cannot access any service in another multiplex, however the same tuner can still serve any of the services in the same multiplex (see also clause C.1.2). Figure 4 shows the dependencies within a hierarchy of <DependencyResourceGroup> elements. Figure 4: Schematic diagram on hierarchy of DependencyResourceGroup elements The schema of the <ServiceAvailabilityMap> is reported in pseudocode 4 and table 4. Pseudocode 4: ServiceAvailabilityMap schema <complexType name="ServiceAvailabilityMapType"> <sequence> <element name="HBLocalServerNode" type="dvbhbam:HBLocalServerNodeType"/> </sequence> <attribute name="version" type="positiveInteger" use="required"/> </complexType> <complexType name="ServiceType"> <attribute name="serviceRef" type="dvbi-types:ServiceIdentifierType" use="required"/> <attribute name="used" type="nonNegativeInteger" use="required"/> <attribute name="transcodedUsed" type="nonNegativeInteger" use="required"/> </complexType> <simpleType name="supportedModulationSystemType"> <restriction base="string"> <enumeration value="DVB-C"/> <enumeration value="DVB-T"/> <enumeration value="DVB-T2"/> <enumeration value="DVB-S"/> <enumeration value="DVB-S2"/> <enumeration value="DVB-S2X"/> </restriction> </simpleType> <complexType name="DependencyResourceGroupType"> <sequence> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 34 <element name="supportedModulationSystem" type="dvbhbam:supportedModulationSystemType" minOccu rs="0" maxOccurs="unbounded"/> <choice> <element name="DependencyResourceGroup" type="dvbhbam:DependencyResourceGroupType" maxOccurs ="unbounded"/> <element name="Service" type="dvbhbam:ServiceType" maxOccurs="unbounded"/> </choice> </sequence> <attribute name="id" type="string" use="required"/> <attribute name="max" type="nonNegativeInteger" use="optional"/> <attribute name="used" type="nonNegativeInteger" use="required"/> </complexType> <complexType name="HBLocalServerNodeType"> <sequence> <element name="supportedModulationSystem" type="dvbhbam:supportedModulationSystemType" minOccu rs="0" maxOccurs="unbounded"/> <element name="DependencyResourceGroup" type="dvbhbam:DependencyResourceGroupType" maxOccurs=" unbounded"/> </sequence> <attribute name="shared" type="boolean" use="optional" default="true"/> <attribute name="totalServedClients" type="nonNegativeInteger" use="required"/> <attribute name="totalServedClientsMax" type="nonNegativeInteger" use="required"/> <attribute name="totalTranscodedClients" type="nonNegativeInteger" use=" required "/> <attribute name="totalTranscodedClientsMax" type="nonNegativeInteger" use=" required "/> <attribute name="totalTranscodedServicesMax" type="nonNegativeInteger" use="required"/> </complexType> Table 4: ServiceAvailabilityMap fields Name Semantic Definition Constraints ServiceAvailabilityMap Root node of the XML document. Mandatory @version Defines the version of the ServiceAvailabilityMap. It shall be identical to the @version of the Availability element described as part of the device capabilities (see table 3) and of the referred DVB-I Service List. Mandatory HBLocalServerNode Node describing the DVB-HB Local Server. Mandatory DependencyResourceGroup Contains all resources elements which are dependent to each other. Mandatory 0 .. ∞ Service Refers to services as described in a DVB-I Service List XML document. This field should be the lowest child element. Mandatory 1 .. ∞ @serviceRef Refers to the entry in the DVB-I Service List. See ETSI TS 103 770 [3] for semantic definition. Mandatory @transcodedUsed Number of clients connected in transcoded mode for the user. This field is used to determine whether a transcoder would be released if the service is released. Mandatory @id Identifier of the DependencyResourceGroup. Mandatory @supportedModulationSystemType Describes the supported modulation system of all subelements. Possible values are: "DVB-T", "DVB-T2"; "DVB-S", "DVB-S2", "DVB-S2X"; "DVB-C". Optional @max Maximum number of usable elements belonging to the DependencyResourceGroup. If there is no limitation, this attribute is omitted. Optional @used Number of used elements belonging to the DependencyResourceGroup. Mandatory @shared Describes whether a tuner can share a service resource. Only relevant with Profile A. Default is "true". Optional @totalServedClients Number of currently served clients. For example, it is relevant in case of bandwidth limitation. Optional @totalServedClientsMax Number of maximally served clients. For example, it is relevant in case of bandwidth limitation. Optional @totalTranscodedClients Number of clients served with a transcoded service on exclusive basis for Profile A. Optional @totalTranscodedClientsMax Number of clients maximally served with a transcoded service on exclusive basis for Profile A. Not relevant for Profile B. Optional @totalTranscodedServicesMax Number of services maximally served with a transcoded service on exclusive basis for Profile B. Not relevant for Profile A. Optional ETSI ETSI TS 104 025 V1.1.1 (2024-07) 35 Pseudocode 5 shows an example of a simple case with two independent tuners available on exclusive basis which can access all services (for simplicity, only 5 services belonging to different multiplexes are listed). In this example, one service (tag:ses.com,2024:daserste.ses.com) is currently served. The described DVB-HB Local Server does not have transcoding capabilities (i.e. it is a Profile A DVB-HB Local Server, since only Profile A DVB-HB Local Servers are not required to transcode). Pseudocode 5: Example of a ServiceAvailabilityMap element with 2 independent tuners and 5 services, no transcoding <?xml version="1.0" encoding="UTF-8"?> <ServiceAvailabilityMap version="2005201628" xmlns="urn:dvb:metadata:dvbhb-availabilitymap:2023" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xsi:schemaLocation="urn:dvb:metadata:dvbhb-availabilitymap:2023 ../schemas/dvbhb- availabilitymap_v1.3.xsd " > <HBLocalServerNode shared="false" totalServedClients="1" totalServedClientsMax="2" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Pseudocode 6 shows the same example but with transcoding capabilities. Pseudocode 6: Example of a ServiceAvailabilityMap element with 2 independent tuners and 5 services and transcoding capabilities <ServiceAvailabilityMap version="2005201628"> <HBLocalServerNode shared="false" totalServedClients="1" totalServedClientsMax="2" totalTranscoded Clients="1" totalTranscodedClientsMax="2" totalTranscodedServicesMax="2"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="1"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> In this example, the DVB-HB Local Server has two independent transcoders. A DVB-HB Client (either a Profile A or Profile B DVB-HB Client) is currently using "Das Erste" service in transcoded mode. The complexity of the ServiceAvailabilityMap structure depends directly on the dependencies among resources. In the simplest case with a single tuner on exclusive basis there would be just two levels, i.e. one <HBLocalServerNode> element containing all services that can be received. Further examples are provided in annex C. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 36 |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4 Management and processing of the Service Availability Map | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.1 Building the Service Availability Map | The hierarchy of the <ServiceAvailabilityMap> element is intended to describe the mutual dependency of several services' usage, whether transcoded or not. Apart from transcoding or limitation on maximum number of clients, only resources which have a mutual impact on each other's usage need to be grouped in the same <DependencyResourceGroup> node. The structure of the Service Availability Map is highly dependent on the configuration of the receiving installation. The number of levels of <DependencyResourceGroup> depends on the configuration. The @id attributes shall be different on each level to be uniquely identified. The ServiceAvailabilityMap.xml document should be available after the installation phase of the DVB-HB Local Server. The actual @serviceRef attribute shall be updated correctly in accordance with the DVB-I formatted Service List. NOTE: To facilitate the installation phase, several beforehand generated ServiceAvailabilityMap.xml versions could be available at product initialization: then only selecting the appropriate ServiceAvailabilityMap.xml version corresponding to the actual configuration would be sufficient. |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.2 Aligning the Service Availability Map with DVB-I Service List updates | A DVB-HB Local Server implementing this feature shall update the <Service> elements in the ServiceAvailabilityMap.xml document to keep it aligned with the DVB-I Service List. Each time the DVB-I Service List is updated and the @version attribute has a new value, the DVB-HB Local Server shall also update the ServiceAvailabilityMap.xml document and the @version attribute accordingly. Rebuilding a complete XML hierarchy by the DVB-HB Local Server is not required, if the internal logic for the generation is stored. For example: • If, within a <DependencyResourceGroup> element, only services of Horizontal polarization and Low band can be received, all services having a Service Instance with these reception parameters are placed here. • If a DVB-HB Local Server contains several independent tuners (i.e. each of the relevant <DependencyResourceGroup> element contains all services), then the updated service list can be directly reflected by updating all <Service> entries in each <DependencyResourceGroup> element. |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.3 Updating the Service Availability Map when assigning a service to a client | A DVB-HB Local Server implementing this feature shall update the usage attributes (i.e. @used, @transcodedUsed, @totalServedClients, @totalTranscodedClients) in the ServiceAvailabilityMap.xml document each time a stream representing a service is delivered to a DVB-HB Client, according to the procedure shown in pseudocode 7 or any alternative algorithm leading to the same result. Pseudocode 7: Algorithm to update the Service Availability Map when assigning a service to a DVB-HB Client Identify all entries containing the service with serviceRef corresponding to the service entry in th e DVB-I formatted service list. if ("shared" is set to false) eliminate serviceRef with used value greater than 0. if (totalServedClients equals totalServedClientsMax) no stream can be provided as the totalClientsServed reached the maximum. EXIT else Increase the totalServedClients by 1 if (a transcoded stream is requested) if (the requested transcoded stream is exclusive) if the totalTranscodedClients value is equal to totalTranscodedClientsMax, no stream can be provided as the totalTranscodedClients reached the maximum. Reverse changes. EXIT ETSI ETSI TS 104 025 V1.1.1 (2024-07) 37 else increase the @totalTranscodedClient attribute on the HBLocalServerNode element for each service entry with serviceRef proceed as follows until a stream can be assigned Increase the value of "transcodeUsed" and "@used" attributes of serviceElement by 1 if (transcodedUsed takes the value 1) calculate totalTranscodedServices by counting services with transcodeUsed > 0 if (totalTranscodedServices equals to totalTranscodedServicesMax) no transcoder is available reverse the change in the loop of this service entry proceed with the next service entry else increase the totalTranscodedServices by 1 foreach DependencyResourceGroup containing the service entry If (one of the elements "@used" attributes of the child element changes from 0 to 1) if ("@used" attribute of the DependencyResourceGroup is equal to "@max" attribute) No DependencyResourceGroup resource is available reverse the changes for this service entry loop proceed with the next service entry else increase the "@used" attribute of the DependencyResoureGroup by 1 A stream corresponding to the requested service could be successfully assigned else for each service entry with serviceRef proceed as follows until a stream can be assigned Increase the value of "transcodeUsed" and "@used" attributes of serviceElement by 1 if (transcodedUsed takes the value 1) calculate totalTranscodedServices by counting services with transcodeUsed > 0 if (totalTranscodedClients value is equal to totalTranscodedClientsMax) no transcoder is available reverse the change in the loop of this service entry loop proceed with the next service entry else increase the @totalTranscodedClient attribute on the HBLocalServerNode element if (totalTranscodedServices equals to totalTranscodedServicesMax) no transcoder is available reverse the change in the loop of this service entry loop proceed with the next service entry else foreach DependencyResourceGroup containing the service entry if (one of the elements "@used" attributes of the child element changes from 0 to 1) if ("@used" attribute of the DependencyResourceGroup is equal to "@max" attribute) No DependencyResourceGroup resource is available reverse the changes for this service entry loop proceed with the next service entry else increase the "@used" attribute of the DependencyResoureGroup by 1 A stream corresponding to the requested service could be successfully assigned else for each service entry with serviceRef proceed as follows until a stream can be assigned Increase the value of "@used" attributes of service Element by 1 foreach DependencyResourceGroup containing the service entry if (one of the elements "@used" attributes of the child element changes from 0 to 1) if ("@used" attribute of the DependencyResourceGroup is equal to "@max" attribute) No DependencyResourceGroup resource is available reverse the changes for this service entry loop proceed with the next service entry else increase the "@used" attribute of the DependencyResoureGroup by 1 A stream corresponding to the requested service could be successfully assigned If (no service resource corresponding to serviceRef can be assigned) the service cannot be assigned 7.3.4.4 Updating the Service Availability Map when releasing a resource used by a client Similarly to updating the ServiceAvailabilityMap.xml document when assigning a service to a DVB-HB Client, releasing a resource can be processed by the DVB-HB Local Server as shown in pseudocode 8. Pseudocode 8: Algorithm to update the Service Availability Map when releasing a resource used by a DVB-HB Client decrement the totalServedClients by 1 if a transcoded stream is released if (the requested transcoded stream was exclusive) decrement the value of "totalTranscodedClient" decrement the value of "transcodeUsed" and "@used" attributes of serviceElement ETSI ETSI TS 104 025 V1.1.1 (2024-07) 38 if (transcodedUsed takes the value 0) decrement "totalTranscodedService" if (the requested transcoded stream was non exclusive) decrement the value of "totalTranscodedClient" foreach DependencyResourceGroup containing the service entry if (one of the elements "@used" attributes of the child element changes from 1 to 0) decrement the value of the "@used" attribute of the DependencyResoureGroup else decrement the value of "@used" attributes of serviceElement foreach DependencyResourceGroup containing the service entry if (one of the elements "@used" attributes of the child element changes from 1 to 0) decrement the value of the "@used" attribute of the DependencyResoureGroup |
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 information message. • Not offering the service on the menu or mark it as unavailable (this may be updated just before building the graphics or afterwards). To assess the actual availability of a resource, a DVB-HB Client implementing this feature shall process the serviceAvailabilityMap.xml document as shown in pseudocode 9, or by any alternative algorithm leading to the same result. Pseudocode 9: Algorithm to verify the availability of services for a DVB-HB Client Update its local copy of ServiceAvailabilityMap.xml with the "simulated" release of its own resource as described in previous clause if (shared equals false) eliminate all services whose attribute "@used" is greater than 0 foreach DepencyResourceGroup of the HBLocalServerNode if ("@used" attribute is equal to "@max" attribute) eliminate all children whose "@used" attribute is equal to 0 foreach Remaining services element if a transcoded stream is requested if service entry has an attribute "@transcodedUsed" equal to 0 if (@totalTranscodedService equals @totalTranscodedServiceMax) eliminate the service entry |
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 be advisable in these circumstances. In this case the @used attribute of the concerned resource is increased by 1. Other DVB-HB Clients may not be able to request a resource as the <DependencyResourceGroup> usage would reach its maximum. With reference to the example shown in pseudocode 5, the DVB-HB Local Server may decide to allocate the second tuner exclusively to one client. In that case, the ServiceAvailabilityMap.xml document may appear as "suboptimal" as two tuners may be used for the same service. 7.3.5 Splitting the ServiceAvailabilityMap.xml document into ServiceAvailabilityIdle.xml and ServiceAvailabilityUpdate.xml The logical structure and dependencies of the Service Availability Map may be quite complex, as it involves all services in one or several instances (e.g. multiple tuners). Reloading the complete ServiceAvailabilityMap.xml by the DVB-HB Client appears unnecessary, since only the @used attributes need to be updated to keep the ServiceAvailabilityMap.xml up-to-date. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 39 For this reason, the ServiceAvailabilityMap.xml shall be split into two files: 1) ServiceAvailabilityMapIdle.xml, whose @used attributes are all set to 0 (i.e. idle mode), 2) ServiceAvailabilityMapUpdate.xml, which contains the actual usage by indicating the updated values of the respective @used attributes. At start time, a DVB-HB Client loads the ServiceAvailabilityMapIdle.xml document. Every time it needs an updated resource usage, it retrieves the ServiceAvailabilityMapUpdate.xml and combines it with the ServiceAvailabilityMapIdle.xml document to obtain the actual ServiceAvailabilityMap.xml. The syntax of ServiceAvailabilityMapUpdate.xml document shall follow IETF RFC 5261 [17]. With reference to the example in pseudocode 5, the ServiceAvailabilityMapIdle.xml document would be as shown in pseudocode 10 and the ServiceAvailabilityMapUpdate.xml document would be as shown in pseudocode 11. When combining them, the result would be according to pseudocode 5. Pseudocode 10: Example of ServiceAvailabilityMapIdle.xml <ServiceAvailabilityMap version="2005201628"> <HBLocalServerNode shared="false" totalServedClients="0" totalServedClientsMax="2" totalTranscoded Clients="0" totalTranscodedClientsMax="2" totalTranscodedServicesMax="2"> <DependencyResourceGroup id="tuner1" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Pseudocode 11: Example of ServiceAvailabilityMapUpdate.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE xml> <diff> <replace sel="ServiceAvailabilityMap/HBLocalServerNode/@totalServedClients">1</replace> <replace sel="ServiceAvailabilityMap/HBLocalServerNode/@totaltranscodedClients">1</replace> <replace sel="ServiceAvailabilityMap/HBLocalServerNode/DependencyResourceGroup[@id='tuner1']@used" >1</replace> <replace sel="ServiceAvailabilityMap/HBLocalServerNode/DependencyResourceGroup[@id='tuner1']/Servi ce[@serviceRef='tag:ses.com,2024:daserste.ses.com'/@used">1</replace> </diff> |
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 availability feature (i.e. some Profile A devices not supporting DVB-I formatted Service Lists are excluded). A DVB-HB Client not supporting this feature can anyway continue to offer all services and will still benefit from DVB-HB Local Server resource sharing; the user will eventually get an error message in case of lack of available resources. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 40 |
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 corresponding LCN key. |
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 Internet-delivered DASH alternative Service Instance of the same service, if also declared in the Service List. |
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 1 and 255. Default value is "1". src=1 Frequency freq Transponder frequency expressed in MHz as fixed point type or integer value. freq=11361.75 freq=11720 Polarization pol Set to one of the following values: • "h" horizontal linear • "v" vertical linear • "l" circular left • "r" circular right pol=h Roll-Off ro Set to one of the following values: • "0.35", "0.25", "0.20", "0.15", "0.10", "0.05". For DVB-S this value shall be set to "0.35" in client queries. For DVB-S2 this value shall be set to "0.35", "0.25" or "0.20" in client queries. ro=0.35 Modulation system msys Set to one of the following values: • "dvbs", "dvbs2", "dvbs2x". msys=dvbs2 Modulation type mtype Set to one of the following values: • "qpsk", "8psk", "8psk-l", "16apsk", "16apsk-l", "32apsk", "32apsk-l", "64apsk", "64apsk-l". For DVB-S this value shall be set to "qpsk" in client queries. For DVB-S2 this value shall be set to "qpsk" or "8psk" in client queries. For DVB-S2X, the possible combinations of mtype and fec shall be according to ETSI EN 302 307-2 [6], table 1. mtype=8psk Pilot tones plts Set to one of the following values: • "on", "off". plts=off ETSI ETSI TS 104 025 V1.1.1 (2024-07) 41 Example of tuning command in case of DVB-S2X and channel bonding over three transponders: SETUP rtsp://192.168.178.57:554/?src=1&fe=1&freq=11013&pol=h&ro=0.20&msys=dvbs2x&mtype=8psk&plts=off &sr=29900&fec=34&cm=ccm&bond=on RTSP/1.0 SETUP rtsp://192.168.178.57:554/?src=1&fe=2&freq=11785&pol=h&ro=0.20&msys=dvbs2x&mtype=16ask&plts=of f&sr=27500&fec=23&cm=ccm&bond=on RTSP/1.0 SETUP rtsp://192.168.178.57:554/?src=1&fe=3&freq=11766&pol=v&ro=0.20&msys=dvbs2x&mtype=8psk&plts=off &sr=29900&fec=34&cm=ccm&bond=last&pids=0,1840,1841,1843 RTSP/1.0 RTSP DESCRIBE and RTP Control Protocol (RTCP) Announcement syntax of EN 50585 [1] are extended as follows: • RTSP DESCRIBE: When supporting DVB-S2X, the attribute syntax in the Session Description Protocol (SDP) implementation is extended as follows: - Session level: s=SatIPServer:1 <sat frontends>,<terr frontends>,<cable frontends> - Media level: For DVB-S this value shall be set to "off" in client queries. Symbol rate sr Value in kSymb/s. sr=27500 FEC inner fec Set to one of the following values: • "12", "23", "34", "56", "78", "89", "35", "45", "910", "14", "13", 25", "1345", "920", "1120", "2336", "2536", "1318". "59", "2645", "2845", "79", "7790", "815", "3245", "1115". For DVB-S this value shall be set to "12", "23", "34", "56" or "78" in client queries. For DVB-S2 this value shall be set to "12", "23", "34", "56", "78", "89", "35", "45" or "910" in client queries. For DVB-S2X, the possible combinations of mtype and fec shall be according to ETSI EN 302 307-2 [6], table 1. fec=23 Modcod mode cm Set to one of the following values: • "ccm", "vcm". Not used for DVB-S and DVB-S2 (default is "ccm"). If provided for DVB-S or DVB-S2, the parameter shall be ignored. cm=ccm Input stream identifier isi Uniquely identifies an Input Stream Identifier. Numerical value between 0 and 255. Not required for DVB-S and DVB-S2. For DVB-S2X, required only if cm is set to "vcm" and multiple Transport Streams are delivered on the transponder. isi=11 Channel bonding bond (see note 1) Set to one of the following values: • "on", "last", "off". Not used for DVB-S and DVB-S2 (default is "off"). If provided for DVB-S or DVB-S2, the parameter shall be ignored. bond=off List of PIDs pids Comma Separated Values (CSV) list of PIDs • Numerical values between 0 and 8191 for Single Programme Transport Stream (SPTS). • "all" for Multi-Programme Transport Stream (MPTS). • "none" for no demux output. Not used for DVB-S and DVB-S2 (default is "off"). If provided for DVB-S or DVB-S2, the parameter shall be ignored. pids=0,16,201,302 addpids (see note 2) Opens new PID filters on the demux for streaming on the network. CSV list of PIDs. addpids=307,309 delpids (see note 2) Removes PID filters from the demux. CSV list of PIDs. delpids=201,302 NOTE 1: In case of channel bonding, client shall send multiple SETUP messages, as shown in the example below. The pids parameters can be included in any of those messages. NOTE 2: The addpids or delpids parameters shall not be used in combination with the pids parameter in the same RTSP query. The addpids and delpids parameters may be combined in the same RTSP query. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 42 a=control:stream=<streamID> a=fmtp:33 ver=1.3;src=<srcID>;tuner=<feID>,<level>,<lock>,<quality>,<frequency>,<pola risation>,<system>,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>,<modcod_mode> ,<isi>,<bond>;pids=<pid0>,…,<pidn> NOTE 1: The version number is set to 1.3. NOTE 2: <sat frontends> provides the number of satellite frontends available from the server (DVB-S plus DVB-S2 plus DVB-S2X). <terr frontends> provides the number of terrestrial frontends available from the server (DVB-T plus DVB-T2). <cable frontends> provides the number of cable frontends available from the server (DVB-C plus DVB-C2). • RTCP APP Packet String Payload Format for DVB-S2X: Similarly to the SDP extension, the APP Packet payload format for RTCP Announcements is extended as follows: ver=1.3;src=<srcID>;tuner=<feID>,<level>,<lock>,<quality>,<frequency>,<polarisation>,<system >,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>,<modcod_mode>,<isi>,<bond>;pids=<pid0 >,…,<pidn> NOTE 3: The version number is set to 1.3. Example text string: ver=1.3;src=1;tuner=1,240,1,7,12402,v,dvbs2x,8psk,,0.20,29900,34,,,;pids=0,16,56,112,168,179 |
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" minOccurs="0"/> <element name="Availability" type="dvbhbx:HBServiceAvailabilityType" minOccurs="0"/> <element name="AL-FEC" minOccurs="0"> <simpleType> <restriction base="string"> <enumeration value="none"/> <enumeration value="baselayer"/> <enumeration value="base+enhancementlayer"/> </restriction> </simpleType> </element> </sequence> </complexType> Table 6: X_SATIP_DVBHB fields Name Semantic Definition Constraints ServiceListOffering A list of details and location of the Service List(s) offered by the DVB-HB Local Server, according to ETSI TS 103 770 [3], clause 5.3.5. Present only if the Profile A DVB-HB Local Server exposes the service list according to the DVB-I format. Optional 0 .. 1 Availability Announces the capabilities of the DVB-HB Local Server in terms of type and number of front-ends (tuners). It also informs about real-time status in terms of used and available resources. See table 3 for semantic definition of HBServiceAvailabilityType. Optional 0 .. 1 AL-FEC Announces the capabilities of the DVB-HB Local Server in terms of support to optional AL-FEC, according to clause 8.4.2. Optional 0 .. 1 ETSI ETSI TS 104 025 V1.1.1 (2024-07) 43 |
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 standards, e.g. Wireless Local Area Network (WLAN)/WIreless FIdelity (Wi-Fi) based on the Institute of Electrical and Electronic Engineers (IEEE) 802.11 family, additional network issues might deteriorate the signal to a level that renders the TS packets, which are sent Quasi Error Free (QEF) by the DVB-HB Local Server (assuming QEF broadcast reception), received by the DVB-HB Client device as damaged and unrecoverable. In the following, an additional option to improve network resilience is defined, based on AL-FEC. |
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 Local Server in the <AL-FEC> element of the <satip-X_DVBHB> element, as described in clause 8.3. If the <AL-FEC> is present and its value is different from none, the DVB-HB Local Server supports AL-FEC as follows: • If the value of the <AL-FEC> element is baselayer, the DVB-HB Local Server supports a Base Layer AL-FEC according to ETSI TS 102 034 [12]. • If the value of the <AL-FEC> element is base+enhancementlayer, the DVB-HB Local Server supports a Base Layer AL-FEC and an Enhanced Layer AL-FEC according to ETSI TS 102 034 [12]. The UDP port of the AL-FEC Base Layer stream shall be equal to the "client RTP port" as per EN 50585 [1] plus 2. The UDP port of the AL-FEC Enhancement Layer stream shall be equal to the "client RTP port" as per EN 50585 [1] plus 4. The RTSP SETUP message defined in EN 50585 [1] is extended with the optional query string parameter &al-fec. EXAMPLE: rtsp://192.168.128.5/?freq=754&bw=8&msys=dvbt&tmode=8k&mtype=64qam&gi=132&fec=23 &pids=0,16,50,201,301&al-fec=baselayer |
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) 44 Figure 5: Functional diagram of AL-FEC generation Lower layer protocols (i.e. UDP encapsulation, Media Access Control (MAC) drivers, etc.) are not involved, and no feedback from the client is required. The solution can be applied on top of any kind of IP network, including any Wi-Fi network of the IEEE 802.11 family. The solution requires direct control of the RTP layer. This is reasonable as: • Profile A DVB-HB Local Servers are expected to control the RTP layer anyway, due to the strict requirements on RTP packet generations given by EN 50585 [1]; • Profile A DVB-HB Clients implementing this optional feature need to access the RTP layer to detect IP packet loss (i.e. retrieving the Sequence Number field in RTP packets header [i.3]). NOTE: In addition to this mechanism based on AL-FEC, Profile A DVB-HB devices may implement additional optimizations at lower layers, leveraging some advanced functions available in specific IEEE 802.11 [i.15] standards. Some background information is given in annex E. |
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 the additional error correction). |
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-I Clients can access a Service List Entry Points document published by the DVB-HB Local Server to retrieve the URL of the relevant DVB-I Service List, but discarding the additional device description and capabilities carried in the <HBLocalServerEntity> element defined in the present document. |
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="en"> DVB-HB extension to dvbi-types:ServiceListEntryPointsType </documentation> </annotation> <complexContent> <extension base="dvbi-types:ExtensionBaseType"> <sequence> <element name="HBLocalServerEntity" type="dvbhbx:HBLocalServerType" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType> Table 7: HBxServiceListEntryPointsType fields Name Semantic Definition Constraints HBLocalServerEntity In case the Service List Entry Points document is published by a DVB-HB Local Server, this element provides description and capabilities of the DVB-HB Local Server. See table 2 for semantic definition of HBLocalServerType. Optional 0 .. 1 |
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 published by a DVB-HB Local Server --> <ServiceListEntryPoints xml:lang="en" xmlns="urn:dvb:metadata:servicelistdiscovery:2024" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:dvb:metadata:servicelistdiscovery:2024 ../schemas/dvbi_service_list_discovery_v1.6.xsd urn:dvb:metadata:dvbhb-extensions:2023 ../schemas/dvbhb-extensions_v1.3.xsd" xmlns:dvbhbx="urn:dvb:metadata:dvbhb-extensions:2023" xmlns:dvbi-types="urn:dvb:metadata:servicediscovery-types:2023"> <ServiceListRegistryEntity> <Name>DVB-HB Local Server Registry</Name> </ServiceListRegistryEntity> <ProviderOffering> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 46 <Provider> <Name>DVB-HB Local Server</Name> </Provider> <ServiceListOffering> <dvbi-types:ServiceListName>DVB-HB Local Server #1</dvbi-types:ServiceListName> <dvbi-types:ServiceListURI contentType="application/xml"> <dvbi-types:URI>http://192.168.1.101/dvbhb/servicelist.xml</dvbi-types:URI> </dvbi-types:ServiceListURI> <dvbi-types:Delivery> <dvbi-types:DASHDelivery required="true"/> </dvbi-types:Delivery> <dvbi-types:ServiceListId>tag:dvbhb-local-server-manufacturer.com,2024:HB-0242ac130003</dvbi- types:ServiceListId> </ServiceListOffering> </ProviderOffering> <Extension xmlns:dvbhbx="urn:dvb:metadata:dvbhb- extensions:2023" xsi:type="dvbhbx:HBxServiceListEntryPointsType" extensionName="DVB-HB"> <dvbhbx:HBLocalServerEntity specVersion="1"> <dvbhbx:DeviceType>urn:dvb:metadata:device:HBLocalServer:1</dvbhbx:DeviceType> <dvbhbx:UniqueDeviceName>uuid:67969aea-73f9-11ea-bc55-0242ac130003</dvbhbx:UniqueDeviceName> <dvbhbx:ModelName>DVB-HB Local Server</dvbhbx:ModelName> <dvbhbx:FriendlyName>Multi-tuner DVB-HB Profile B Local Server</dvbhbx:FriendlyName> <dvbhbx:Manufacturer>DVB-HB Local Server Manufacturer</dvbhbx:Manufacturer> <dvbhbx:SerialNumber>HB-0242ac130003</dvbhbx:SerialNumber> <dvbhbx:ManufacturerURL>http://www.dvbhb-localserver-manufacturer.com</dvbhbx:ManufacturerURL> <dvbhbx:Availability version="1"> <dvbhbx:ServiceAvailabilityMapIdleURL contentType="application/xml"> <dvbi-types:URI>http://192.168.1.101/dvbhb/ServiceAvailabilityMapIdle.xml</dvbi-types:URI> </dvbhbx:ServiceAvailabilityMapIdleURL> <dvbhbx:ServiceAvailabilityMapUpdateURL contentType="application/xml"> <dvbi-types:URI>http://192.168.1.101/dvbhb/ServiceAvailabilityMapUdpate.xml</dvbi- types:URI> </dvbhbx:ServiceAvailabilityMapUpdateURL> </dvbhbx:Availability> </dvbhbx:HBLocalServerEntity> </Extension> </ServiceListEntryPoints> 9.3 Identification of services originated by the DVB-HB Local Server |
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 the dvbisd:DASHDeliveryParametersType element of ETSI TS 103 770 [3]. NOTE: Legacy DVB-I Clients can access an extended <DASHDeliveryParameters> element, included in a DVB-I Service List published by the DVB-HB Local Server, to retrieve the URL of the relevant DASH MPD, but discarding the additional identification of the source. |
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:lang="en"> DVB-HB extension to dvbi-types:DASHDeliveryParametersType </documentation> </annotation> <complexContent> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 47 <extension base="dvbi-types:ExtensionBaseType"> <sequence> <element name="OriginalDeliverySource" minOccurs="0"> <simpleType> <restriction base="anyURI"> <enumeration value="urn:dvb:metadata:source:dvb-t"/> <enumeration value="urn:dvb:metadata:source:dvb-s"/> <enumeration value="urn:dvb:metadata:source:dvb-c"/> </restriction> </simpleType> </element> </sequence> </extension> </complexContent> </complexType> Table 8: HBxDASHDeliveryParametersType fields Name Semantic Definition Constraints OriginalDeliverySource If this service instance is generated by a DVB-HB Local Server, identifies the original delivery source for this service instance. Possible values are: urn:dvb:metadata:source:dvb-t, urn:dvb:metadata:source:dvb-s, urn:dvb:metadata:source:dvb-c. Optional 0 .. 1 |
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.com,2024:HB-0242ac130003" xmlns="urn:dvb:metadata:servicediscovery:2024" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:dvb:metadata:servicediscovery:2024 ../schemas/dvbi_v6.0.xsd urn:dvb:metadata:dvbhb-extensions:2023 ../schemas/dvbhb-extensions_v1.3.xsd" xmlns:dvbhbx="urn:dvb:metadata:dvbhb-extensions:2023" xmlns:dvbi-types="urn:dvb:metadata:servicediscovery-types:2023"> <Name>Example of DASH service instance published by a DVB-HB Local Server</Name> <ProviderName>HB Local Server</ProviderName> <Service version="1"> <UniqueIdentifier>tag:192.168.1.101,2024:dvb-s/318.5200.3401/service1</UniqueIdentifier> <ServiceInstance> <DASHDeliveryParameters> <UriBasedLocation contentType="application/dash+xml"> <dvbi-types:URI>http://192.168.1.101/dash/11766V_service1.mpd</dvbi-types:URI> </UriBasedLocation> <Extension xmlns:dvbhbx="urn:dvb:metadata:dvbhb- extensions:2023" xsi:type="dvbhbx:HBxDASHDeliveryParametersType" extensionName="DVB-HB"> <dvbhbx:OriginalDeliverySource>urn:dvb:metadata:source:dvb-s </dvbhbx:OriginalDeliverySource> </Extension> </DASHDeliveryParameters> </ServiceInstance> <ServiceName>Service1</ServiceName> <ProviderName>Provider1</ProviderName> </Service> </ServiceList> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 48 10 Conversion of DVB-SI metadata to DVB-I format (informative) |
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], carried in the input TS as received at the reference point T (see also clause 5). In the following, description on how to map some of the SI fields to DVB-I metadata is provided. Alternatively, the generation of the service list in a DVB-I compatible format (or part of it) may rely on an external repository, as described in clause 5.4.12. It is recommended that the DVB-I metadata is always aligned with the actual SI. NOTE: The acquisition time, which is dependent on repetition rates of the SI within a broadcast signal, can affect the generation or update of local DVB-I metadata. |
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 names can be specified as long as they have different @xml:lang values) SDT service_descriptor as defined in ETSI EN 300 468 [18], clause 6.2.36 service_name multilingual_service_name_ descriptor as defined in ETSI EN 300 468 [18], clause 6.2.25 service_name Service.ProviderName (multiple service provider names can be specified as long as they have different @xml:lang values) service_descriptor as defined in ETSI EN 300 468 [18], clause 6.2.36 provider_name multilingual_service_name_ descriptor as defined in ETSI EN 300 468 [18], clause 6.2.25 provider_name Service.ServiceType and Service.ServiceInstance.ContentAttributes See ETSI TS 103 770 [3], table D.1 |
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 ServiceList.ContentGuideSource element (or in the Service.ContentGuideSource elements, if different for the different services) in the published DVB-I Service List. Alternatively, the Content Guide server functionality may rely on a remote server on the cloud. It is recommended that the DVB-I Content Guide metadata is always aligned with the actual SI Event Information Table (EIT). NOTE: The acquisition time, which is dependent on repetition rates of the SI within a broadcast signal, can affect the generation or update of local DVB-I metadata. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 49 A DVB-HB Local Server should construct the Content Guide metadata from the SI information. Table 10 lists the correspondence between the main Content Guide metadata items and the SI fields. Table 10: Association of SI EIT fields with DVB-I Content Guide elements DVB-I Content Guide element SI table SI descriptor SI field ProgramDescription.ProgramLocationTable .Schedule@serviceIDRef (set to the UniqueIdentifier of the corresponding service in the Service List) EIT - service_id Not available. Content Guide is pulled by client on request and not pushed by server. - version_number ProgramDescription.ProgramLocationTable .Schedule.ScheduleEvent.Program@crid and ProgramDescription.ProgramInformationTable .ProgramInformation@programId - event_id ProgramDescription.ProgramLocationTable .Schedule.ScheduleEvent.PublishedStartTime - start_time ProgramDescription.ProgramLocationTable .Schedule.ScheduleEvent.PublishedDuration - duration ProgramDescription.ProgramInformationTable .BasicDescription.Synopsis (with @length="medium") short_event_descriptor event_name ProgramDescription.ProgramInformationTable .BasicDescription.CreditsLists or ProgramDescription.ProgramInformationTable .BasicDescription.Synopsis (with @length="long") extended_event_descriptor item_description and item See table 9 component_descriptor ProgramDescription.ProgramInformationTable .BasicDescription.Genre content_descriptor ProgramDescription.ProgramInformationTable .BasicDescription.ParentalGuidance.MinimumAge parental_rating_descriptor rating |
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:metadata:2024" xmlns:mpeg7="urn:tva:mpeg7:2008" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:tva:metadata:2024 ../schemas/tva_metadata_3-1.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xml:lang="eng"> <ProgramDescription> <ProgramInformationTable xml:lang="eng"> <ProgramInformation programId="crid://service1/now"> <BasicDescription> <Title type="main">Title of current programme</Title> <Synopsis length="medium">Description of current programme</Synopsis> <ParentalGuidance> <mpeg7:MinimumAge>14</mpeg7:MinimumAge> </ParentalGuidance> </BasicDescription> </ProgramInformation> <ProgramInformation programId="crid://service1/next"> <BasicDescription> <Title type="main">Title of next programme</Title> <Synopsis length="medium">Description of next programme</Synopsis> <ParentalGuidance> <mpeg7:MinimumAge>0</mpeg7:MinimumAge> </ParentalGuidance> </BasicDescription> </ProgramInformation> </ProgramInformationTable> <ProgramLocationTable xml:lang="eng"> <Schedule serviceIDRef="service1" start="2023-07-17T10:57:00Z" end="2023-07-17T12:12:00Z"> <ScheduleEvent> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 50 <Program crid="crid://service1/now"/> <PublishedStartTime>2023-07-17T10:57:00Z</PublishedStartTime> <PublishedDuration>PT45M</PublishedDuration> </ScheduleEvent> <ScheduleEvent> <Program crid="crid://service1/next"/> <PublishedStartTime>2023-07-17T11:42:00Z</PublishedStartTime> <PublishedDuration>PT30M</PublishedDuration> </ScheduleEvent> </Schedule> </ProgramLocationTable> </ProgramDescription> </TVAMain> |
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 based on the transmitted logical channel descriptors, potentially bouquet selection or subscription level and potentially regionalization information and associated rules. A DVB-HB Local Server should be able to extract this information from the broadcast transmission and to generate corresponding metadata. NOTE: It is understood that supporting various rules, syntaxes, etc. may be felt as challenging by a manufacturer, although implemented in conventional IRDs. IRDs may implement subset of these features (e.g. only LCNs without regional descriptors, no simulcast processing, etc.). With some exceptions, all these elements are defined outside DVB and there is no unique correspondence that can be defined in a specification. However, some elements are provided below on how to construct an ordered service list: 1) Generate the <service> element - Gather all services as a result of a scan of SDTactual/SDTother, private tables, private descriptors or other transmitted data. - Identify duplicate identical instances of the same service. These duplicates have identical audio/video coding and same editorial content at all times. Duplicates should be deleted or inserted as alternate <ServiceInstance> elements under the same <Service> element. 2) Identify the Regions and the Subscription Packages - In the input TS, according to ETSI EN 300 468 [18], regions can be defined as target regions, channel lists, bouquet sections, network sections. Hence, name can be extracted from target region descriptor, channel list names, bouquet names, multilingual bouquet names, network names, network identifiers. - Subscription Package may be defined in channel lists, bouquet sections or network sections. 3) Merge Service Instances associated to the same editorial content into the same <Service> element - Identify all instances of the same service and merge each instance as a <ServiceInstance>. There may be several non-identical instances of the same service, that always carry the same editorial content but differ in their audio/video coding or format (simulcast). Those instances use the same LCN, Simulcast Event Descriptor, a service replacement descriptor, the same or similar instance name. The priority (i.e. @priority attribute of the <ServiceInstance> element) is defined according to respective rules associated with the LCN syntaxes. 4) Generate the <LCNTable> element - If different LCN values result from the combination of a Subscription Package and region, generate an LCNTable for each pair of region and Subscription Package. - If different LCN values result from different Subscription Packages, generate an LCNTable for each Subscription Package. - If different LCN values result from different regions, generate an LCNTable for each region. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 51 - If different bouquets representing Subscription Package and different regions, generate an LCNTable for each pair of region and Subscription Package. 5) Address services without LCN or outside a service_list_descriptor - For a given LCNTable, services without an LCN can be placed at the end of last assigned LCN or in a specific range. - If a service_list_descriptor is present, services not present in the service_list_descriptor should be removed from the LCNTable. Table 11 lists the association of some of the fields of the SI tables with the elements in the output DVB-I Service List. Table 11: Association of Logical Channel Numbers distributed over DVB broadcast signalling with DVB-I Service List elements DVB-I service discovery element SI table and field RegionList.Region.RegionName LCNTable.TargetRegion corresponding to respective @regionId "Regions" as delivered via broadcast signalling (examples: postcodes, indexes, names, etc.) LCNTable.SubscriptionPackage Subscription Package as delivered via broadcast signalling LCNTable.LCN@channelNumber with @serviceRef set to the UniqueIdentifier of the corresponding service in the Service List Logical Channel Numbers distributed over broadcast signalling In cases where it can be assumed that all DVB-HB Clients in the LAN are associated with the same region (i.e. the region where the DVB-HB Local Server is installed) and the same Subscription Package, a DVB-HB Local Server may simplify the generation and maintenance of the Service List by applying user selection of a single region and Subscription Package during the configuration phase of the device. 10.5 Mandatory elements of the DVB-I Service List in the absence of corresponding SI metadata or not specified in the received SI metadata Not all elements in the DVB-I Service List can be directly derived from SI metadata. Table 12 provides suggestions on how a DVB-HB Local Server can complete the DVB-I Service List by including at least all mandatory elements according to ETSI TS 103 770 [3]. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 52 Table 12: Generation of DVB-I Service List mandatory elements DVB-I service discovery element Description ServiceList.Name Manufacturer's choice. It is the value shown on the client UI. ServiceList.ProviderName Manufacturer's choice. It may be shown on the client UI. ServiceList@version Integer value, defined by the DVB-HB Local Server, incremented at each change in the Service List. ServiceList@id Unique ID of the Service List. It is the same value as in ServiceListEntryPoints.ServiceListId. Refer to ETSI TS 103 770 [3], clause 5.2.2 for the suitable formats. Service.UniqueIdentifier Unique ID of the service. Refer to ETSI TS 103 770 [3], clause 5.2.2 for the suitable formats. For instance, the DVB-HB Local Server may construct it on the basis of on-air parameters (e.g. tag:192.168.1.101,2024:dvb- s/318.5200.3401/service1, i.e. using DVB triplet + service name). A DVB-HB Local Server relying on an external repository (see clause 5.4.12) may use the same UniqueIdentifier as used in public DVB-I Service Lists for the same service. Service.ServiceName See table 9. Service.ProviderName See table 9. Service@version Integer value, defined by the DVB-HB Local Server, incremented at each change in the Service definition. ContentGuideSource.ProviderName Manufacturer's choice. It may be shown on the client UI. ContentGuideSource.ScheduleInfoEndpoint See clause 10.3. LCNTableEntry@channelNumber See table 11. LCNTableEntry@serviceRef See table 11. DASHDeliveryParameters.UriBasedLocation The DVB-HB Local Server can autonomously define the URL associated to each service. For instance, the URL may be related to tuning parameters (e.g. similar format to RTSP commands in SATellite over Internet Protocol (SAT>IP®) [1]), or may be assigned according to different criteria. 11 Considerations on the use of HTTP and HTTPS in combination with browser-based DVB-HB Clients (informative) |
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 Server of content and metadata on the LAN in a way that can be also handled by browser-based DVB-HB Clients, using technologies such as HTML5 and JavaScript. Objects fetched via HTTP or HTTPS could be: • The HTML5+JavaScript DVB-HB Client itself. • The Service List Entry Points (see also clause 9.2). • The Service List. • DASH-delivered audio/video streams. The use of HTTP and HTTPS in combination with browser-based DVB-HB Clients may have technical implications. Additionally, in modern browsers, access to resources in the private network by an app loaded from a different origin may be restricted by security policies. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 53 |
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 9110 [i.5]), as TLS is designed to be protocol-independent (IETF RFC 8446 [i.4]). The security of TLS is guaranteed by fulfilling the following communication properties: • Authentication (of the server side and, optionally, of the client side). • Confidentiality (i.e. data is visible only at the endpoints). • Integrity (i.e. data cannot be modified by attackers). The above properties are dependent on the parameters/messages exchanged during the TLS handshake phase, where the following tasks are performed in an attacker-resistant fashion: • Authentication of communicating parties by means of Certificate Authority (CA) certificates issued by trusted authorities; • Cryptographic modes negotiation (to encrypt transmitted data); • Shared keying material transmission. NOTE: The current version of TLS is 1.3, which supersedes and obsoletes previous versions by defining new procedures for TLS ticket mechanism, keys derivation and Online Certificate Status Protocol (OSCP) messages exchange. The present document implies the use of TLS 1.3 unless otherwise stated. Given its level of security, HTTPS is now a requirement for most apps and web pages. Many HTTP Streaming technologies are moving to HTTPS content delivery to be compatible with HTTPS platforms/apps. The reason behind this is that almost the entirety of modern web browsers does not allow mixing of HTTP and HTTPS resources (as known as Mixed content, see clause 11.3.2) as this would expose the unencrypted, clear text HTTP content to sniffers and man-in-the middle attacks. Some browsers still allow mixed content only from the localhost, but most of them do not allow this practice at all. From a DVB-HB standpoint, this represents a significant technical issue, because, on one hand, a successful and secure service delivery endorses the use of HTTPS, but, on the other hand, since 2015 CAs can no longer issue publicly-trusted certificates for any host name that cannot be publicly verified (i.e. internal names) and/or which contains a reserved IP address (IETF RFC 1918 [i.6]) (both these cases represent typical LAN and home networks scenarios). This change was deemed necessary to address some security vulnerabilities, including but not limited to: • Non-uniqueness of internal names and, therefore, of the associated certificates. • Non-verifiability of internal names from CAs. • Address Resolution Protocol (ARP) spoofing. • Dynamic Host Configuration Protocol (DHCP) spoofing. • DNS cache poisoning. • Exposure to attacks for hosts with internal Fully Qualified Domain Name (FQDN). It is also worth mentioning that some modern browsers implement the Private Network Access specification [i.7], which prevents public network resources from requesting private network resources, unless the public network resource is secure (HTTPS) and the private network resource provides appropriate Cross-Origin Resource Sharing (CORS) headers. In the context of DVB-HB, this is relevant in case the DVB HB Client HTML5+JavaScript code is loaded from the web (see also clause 11.3.5). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 54 |
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 Local Server, which is located in the same LAN as the DVB-HB Client, can be considered a secure source and therefore it is allowed to expose its metadata either over HTTP or HTTPS. NOTE: A growing number of features in modern browsers Application Programming Interface (API) are migrating to secure-only origins (HTTPS) as HTTP is gradually being marked as non-secure. One of those features, particularly relevant for video consumption, is Encrypted Media Extensions (EME), which is involved in the playback of encrypted audio and video [i.8]. |
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 allowed to fetch resources (e.g. the Service List, or DASH-delivered audio/video streams) from a DVB-HB Local Server as HTTP, but is forced to use HTTPS. This is known as mixed content issue and can be divided in two categories: • Mixed passive/display content. Less harmful for the user. Passive contents include <img> and <video> elements/requests. User-agents can decide to handle this type of mixed content as optionally-blockable when the risk of allowing its usage is outweighed by the risk of breaking significant portions of the web (see also [i.9]). • Mixed active content. It has access to the whole Document Object Model (DOM) of the HTTPS page and can modify its behaviour (potentially including malicious JavaScript code). Active content includes <script>, <iframe> and XMLHttpRequest elements/requests. This type of mixed content is usually blocked by all user- agents. TLS support by the DVB-HB Local Server is the only way to overcome the mixed content issue. NOTE: It is worth mentioning that also mobile operating systems are starting to mandate the use of HTTPS connections for their apps, hence this requirement will be relevant in the future also for app-based clients. To fulfil this, DVB-HB Local Servers and DVB-HB Clients operating in the LAN should support the authentication mechanism of the communicating parties. This mechanism relies on the presence of a certificate issued by a trusted CA that is transmitted from the server to the client during the handshake procedure. However, for a DVB-HB Local Server, issuing a certificate would not be possible, as, according to the CA/Browser Forum Baseline Requirements [i.10]: "The CA MUST confirm that the Applicant controls the Fully-Qualified Domain Name (FQDN) or IP address or has been granted the right to use it by the Domain Name Registrant or IP address assignee, as appropriate. Wildcard FQDNs are permitted. As of the Effective Date of these Requirements, prior to the issuance of a Certificate with a subjectAlternativeName extension or Subject commonName field containing a Reserved IP Address or Internal Name, the CA SHALL notify the Applicant that the use of such Certificates has been deprecated by the CA / Browser Forum and that the practice will be eliminated by October 2016. Also as of the Effective Date, the CA SHALL NOT issue a certificate with an Expiry Date later than 1 November 2015 with a subjectAlternativeName extension or Subject commonName field containing a Reserved IP Address or Internal Name. Effective 1 October 2016, CAs SHALL revoke all unexpired Certificates whose subjectAlternativeName extension or Subject commonName field contains a Reserved IP Address or Internal Name." In other words, the CAs are not allowed to issue publicly-trusted certificates to devices operating in the LAN. Since obtaining a TLS server certificate for a DVB-HB Local Server has become a non-trivial task in recent years, in the next clauses the possible approaches to overcome this issue are suggested. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 55 |
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 this solution are out of scope of the present document, but a plethora of options and open- source solutions exist at the time of this writing. NOTE: Even if the CA/Browser Forum does not prohibit the enterprise and private use of self-signed certificates, this approach does not provide the same level of security that a certificate signed by a publicly trusted CA is able to guarantee. This, therefore, may result in web browser warnings on browser-based clients, while native clients may be configured to allow TLS with self-signed certificates by default. |
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 new wildcard-capable and unique intermediate certificate to be issued for every DVB-HB Local Server by signing a commercial agreement with a valid CA. • A DNS server supporting Distributed Domain Name System (DDNS) hosted for DVB-HB purposes at a known public domain (e.g. dvbhbdns.host). • A recognized hashing algorithm to provide each DVB-HB Local Server with a unique key (HASH). The main steps for this approach are the following: 1) Set up a DDNS space on the DNS server. 2) Issue a wildcard-capable intermediate certificate for the DVB-HB Local Server during the initial setup. The intermediate certificate should have the address in the form: *.HASH.DOMAIN where: - HASH is the unique key, uniquely identifying the DVB-HB Local Server (e.g. it can be the UniqueDeviceName as defined in clause 7.2). - DOMAIN is the public domain of the DNS server (e.g. dvbhbdns.host). 3) At setup time, or every time the DVB-HB Local Server changes its local IP address, prompt a DDNS update request from the DVB-HB Local Server to the DNS server. The update should allow to resolve any IP.HASH.DOMAIN to the IP address, where: - IP is the server's private IP address. This address may change frequently depending on the local network conditions. - HASH is the unique key, uniquely identifying the DVB-HB Local Server. - DOMAIN is the public domain of the DNS server (e.g. dvbhbdns.host). NOTE: In this approach IP and HASH have to be known by the user by following the DVB-HB Local Server discovery phase (see also clause 6). An example of this implementation is represented in figure 6. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 56 Figure 6: DVB-HB Local Server with TLS intermediate certificate The advantages of this method are: • The DNS setup allows to be redirected to any (i.e. public or private) IP address using HTTP over TLS. • The wildcard certificate is valid independently of the IP address used (i.e. public or private). • The HASH guarantees the uniqueness of the DVB-HB Local Server, which is of pivotal importance for the security of the authentication process. • The DOMAIN can be any, therefore it should not be a problem to obtain the domain validation. A drawback of this approach is that the DVB-HB Client has to know in advance that the DVB-HB Local Server uses a TLS intermediate certificate, so that it can start the process by querying the DDNS. This approach is preferably coupled with a DVB-HB Local Server discovery mechanism based on a remote authentication server (see clause 6.3.4). |
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 unintentional exposure of devices and servers on a client's internal network to the Internet. Private network requests are those whose target server's IP address is more private than the IP address from which the request initiator was fetched. For example, a request from a public website (https://example.com) to a private website (http://router.local), or a request from a private website to localhost. If a website needs to issue requests to a target server on a private IP address, then simply upgrading the initiator website to HTTPS would not work, as mixed content prevents secure contexts from making requests over HTTP. There are a few ways to solve this issue [i.11]: • Upgrade both ends to HTTPS, with the implications described in clause 11.3.2, clause 11.3.3 and clause 11.3.4. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 57 • Reverse the embedding relationship, i.e. instead of fetching private resources from a public web app, a skeleton of the app (e.g. an HTML file) can be served from a server on the private network, which then fetches all its subresources (such as scripts or images) from a public server. The resulting web app can then make requests to the private server, as these are considered coming from the same origin. NOTE: In this case, it is assumed that the IP address of the server hosting the skeleton of the app is known by other means. • CORS preflight requests [i.7], i.e. even when the request was initiated from a secure context, the target server is asked to provide an explicit grant to the initiator. A browser implementing this feature sends a preflight request before the actual HTTP request, including an Access-Control-Request-Private-Network: true header in addition to other CORS request headers. The server responds with an Access-Control-Request- Private-Network: true header to explicitly indicate that it grants access to the resource. |
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 CPUs, hardware accelerated decoding and, potentially, hardware accelerated encoding with one single video encoding capability. Audio encoding is more lightweight and might be performed as software encoding. Elementary recommendations for packaging and/or encoding by a DVB-HB Local Server are provided. Basically, two options are possible: • Simple repackaging as DASH without transcoding. • Transcoding and packaging as DASH. |
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 interoperability with a larger device population. Choosing these parameters does not preserve the original quality of the broadcast service (beyond the losses inferred by transcoding). It is a DVB-HB Local Server manufacturer's choice to decide the strategy to choose. Ideally, both profiles should be offered - with and without transcoding to the recommended interoperability points. |
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 repackaging the TS video to demultiplexed video into ISO BMFF format segments according to ETSI TS 103 285 [2]. Demultiplexing, segmentation and remultiplexing in ISO BMFF are lightweight processes that can be implemented in software, together with the corresponding MPD, expected to be relatively static. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 58 Benefit is that the original broadcast quality is preserved with low resources. Also, DVB-HB Local Servers not equipped with an encoder could offer at least some services in DVB-I compliant format. Another possibility is to use this method to serve some DVB-HB Clients with some services, saving encoding resources to serve other DVB-HB Clients that request services which cannot be repackaged without encoding, or are not supporting the interoperability points referred to as above. The drawbacks are that repackaging keeps the same bit-rate as the incoming broadcast signal, which might be challenging for delivery within the home in some cases. Furthermore, the segment length is related to the Random Access Point (RAP) interval, which may lead to larger delays. Finally, received broadcast signals that are encoded in MPEG-2 are assumed not to be supported, as MPEG-2 video is not part of ETSI TS 101 154 [11], annex L. Also, simple repackaging leads to unaligned audio and video segments. The only solution to obtain aligned segments would be to re-encode audio and video with the same audio and video segment length multiple of the duration between RAPs and either a multiple of audio frames (if the audio codec uses audio frames) or a multiple of the duration between two samples (equal to reciprocal of sample frequency). |
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 sample analysis conducted on terrestrial services and satellite services encoded in AVC (720p50 or 1080i50) during a 10 minutes observation time. Table 13: Analysis of RAP spacing in broadcast services Service Video format Seconds between RAPs "Hessen Fernsehen HD" 720p50 0,02 - 0,78 (0,02 s steps) "ARTE" 1080i50 0,04 - 1,28 (0,04 s steps) "C8" 1080i50 0,12 - 1,44 (0,04 s steps) Such a characteristic can be used to define segments which are in the order of 1 s. ETSI TS 103 285 [2] allows indeed a variation of 50 % in segment length. In the MPD a duration of 2 s can be used, which would allow a variation of up to 1 s. A DVB-HB Local Server can then group the GOP in a way that the segment stays close to 1 s. |
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 s. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 60 Annex A (normative): Schemas A.1 DVB-HB extensions Pseudocode A.1: Schema of DVB-HB extensions <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:dvbi-types="urn:dvb:metadata:servicediscovery-types:2023" xmlns:dvbhbx="urn:dvb:metadata:dvbhb-extensions:2023" xmlns:mpeg7="urn:tva:mpeg7:2008" xmlns:tva="urn:tva:metadata:2024" targetNamespace="urn:dvb:metadata:dvbhb- extensions:2023" elementFormDefault="qualified" attributeFormDefault="unqualified"> <import namespace="urn:tva:metadata:2024" schemaLocation="tva_metadata_3-1.xsd"/> <import namespace="urn:tva:mpeg7:2008" schemaLocation="tva_mpeg7.xsd"/> <import namespace="urn:dvb:metadata:servicediscovery-types:2023" schemaLocation="dvbi_types_v1.0.xsd"/> <!-- Extension to ServiceListEntryPoints (for Profile B) --> <complexType name="HBxServiceListEntryPointsType" abstract="false"> <annotation> <documentation xml:lang="en"> DVB-HB extension to dvbi-types:ServiceListEntryPointsType </documentation> </annotation> <complexContent> <extension base="dvbi-types:ExtensionBaseType"> <sequence> <element name="HBLocalServerEntity" type="dvbhbx:HBLocalServerType" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType> <complexType name="HBLocalServerType"> <sequence> <element name="DeviceType" type="anyURI"/> <element name="UniqueDeviceName"> <simpleType> <restriction base="string"> <pattern value="uuid:[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}"/> </restriction> </simpleType> </element> <element name="UniversalProductCode" minOccurs="0"> <simpleType> <restriction base="string"> <pattern value="[0-9]{12}"/> </restriction> </simpleType> </element> <element name="ModelName" type="mpeg7:TextualType"/> <element name="FriendlyName" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="Manufacturer" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="ModelNumber" type="mpeg7:TextualType" minOccurs="0"/> <element name="SerialNumber" type="mpeg7:TextualType" minOccurs="0"/> <element name="ModelDescription" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/ > <element name="ManufacturerURL" type="anyURI" minOccurs="0"/> <element name="ModelURL" type="anyURI" minOccurs="0"/> <element name="Icon" type="tva:RelatedMaterialType" minOccurs="0" maxOccurs="unbounded"/> <element name="Availability" type="dvbhbx:HBServiceAvailabilityType" minOccurs="0"/> </sequence> <attribute name="specVersion" type="positiveInteger" use="required"/> </complexType> <!-- used for both Profiles A and B --> <complexType name="HBServiceAvailabilityType"> <sequence> <element name="OrbitalPosition" type="dvbi-types:LongitudeType" minOccurs="0" maxOccurs="unbounded"/> <element name="ServiceAvailabilityMapIdleURL" type="dvbi-types:ExtendedURIType"/> <element name="ServiceAvailabilityMapUpdateURL" ETSI ETSI TS 104 025 V1.1.1 (2024-07) 61 type="dvbi-types:ExtendedURIType" minOccurs="0"/> </sequence> <attribute name="version" type="positiveInteger" use="required"/> </complexType> <!-- Additions to desc.xml (for Profile A) --> <complexType name="X_SATIP_DVBHB"> <sequence> <element name="ServiceListOffering" type="dvbi-types:ServiceListOfferingType" minOccurs="0"/> <element name="Availability" type="dvbhbx:HBServiceAvailabilityType" minOccurs="0"/> <element name="AL-FEC" minOccurs="0"> <simpleType> <restriction base="string"> <enumeration value="none"/> <enumeration value="baselayer"/> <enumeration value="base+enhancementlayer"/> </restriction> </simpleType> </element> </sequence> </complexType> <complexType name="HBxDASHDeliveryParametersType" abstract="false"> <annotation> <documentation xml:lang="en"> DVB-HB extension to dvbi-types:DASHDeliveryParametersType </documentation> </annotation> <complexContent> <extension base="dvbi-types:ExtensionBaseType"> <sequence> <element name="OriginalDeliverySource" minOccurs="0"> <simpleType> <restriction base="anyURI"> <enumeration value="urn:dvb:metadata:source:dvb-t"/> <enumeration value="urn:dvb:metadata:source:dvb-s"/> <enumeration value="urn:dvb:metadata:source:dvb-c"/> </restriction> </simpleType> </element> </sequence> </extension> </complexContent> </complexType> </schema> A.2 DVB-HB Service Availability Map Pseudocode A.2: ServiceAvailabilityMap schema <?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:dvbhbam="urn:dvb:metadata:dvbhb-availabilitymap:2023" xmlns:dvbi-types="urn:dvb:metadata:servicediscovery-types:2023" targetNamespace="urn:dvb:metadata:dvbhb- availabilitymap:2023" elementFormDefault="qualified" attributeFormDefault="unqualified"> <import namespace="urn:dvb:metadata:servicediscovery-types:2023" schemaLocation="dvbi_types_v1.0.xsd"/> <element name="ServiceAvailabilityMap" type="dvbhbam:ServiceAvailabilityMapType"/> <complexType name="ServiceAvailabilityMapType"> <sequence> <element name="HBLocalServerNode" type="dvbhbam:HBLocalServerNodeType"/> </sequence> <attribute name="version" type="positiveInteger" use="required"/> </complexType> <complexType name="ServiceType"> <attribute name="serviceRef" type="dvbi-types:ServiceIdentifierType" use="required"/> <attribute name="used" type="nonNegativeInteger" use="required"/> <attribute name="transcodedUsed" type="nonNegativeInteger" use="required"/> </complexType> <simpleType name="supportedModulationSystemType"> <restriction base="string"> <enumeration value="DVB-C"/> <enumeration value="DVB-T"/> <enumeration value="DVB-T2"/> <enumeration value="DVB-S"/> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 62 <enumeration value="DVB-S2"/> <enumeration value="DVB-S2X"/> </restriction> </simpleType> <complexType name="DependencyResourceGroupType"> <sequence> <element name="supportedModulationSystem" type="dvbhbam:supportedModulationSystemType" minOccu rs="0" maxOccurs="unbounded"/> <choice> <element name="DependencyResourceGroup" type="dvbhbam:DependencyResourceGroupType" maxOccurs ="unbounded"/> <element name="Service" type="dvbhbam:ServiceType" maxOccurs="unbounded"/> </choice> </sequence> <attribute name="id" type="string" use="required"/> <attribute name="max" type="nonNegativeInteger" use="optional"/> <attribute name="used" type="nonNegativeInteger" use="required"/> </complexType> <complexType name="HBLocalServerNodeType"> <sequence> <element name="supportedModulationSystem" type="dvbhbam:supportedModulationSystemType" minOccu rs="0" maxOccurs="unbounded"/> <element name="DependencyResourceGroup" type="dvbhbam:DependencyResourceGroupType" maxOccurs=" unbounded"/> </sequence> <attribute name="shared" type="boolean" use="optional" default="true"/> <attribute name="totalServedClients" type="nonNegativeInteger" use="required"/> <attribute name="totalServedClientsMax" type="nonNegativeInteger" use="required"/> <attribute name="totalTranscodedClients" type="nonNegativeInteger" use=" required "/> <attribute name="totalTranscodedClientsMax" type="nonNegativeInteger" use=" required "/> <attribute name="totalTranscodedServicesMax" type="nonNegativeInteger" use="required"/> </complexType> </schema> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 63 Annex B (normative): Electronic attachments The present document includes an electronic attachment, contained in ts_104025v010101p0.zip, with the following contents: • dvbhb-extensions_v1.3.xsd - Extensions to EN 50585 [1] and DVB-I [3] schemas for DVB-HB, as shown in clause A.1. • dvbhb-availabilitymap_v1.3.xsd - Schema of Service Availability Map (see clause 7.3.3), as shown in clause A.2. • dvbi_types_v1.0.xsd - DVB-I datatypes used in service list discovery and concrete types for service list extensions (imported into dvbhb-extensions_v1.3.xsd and dvbhb-availabilitymap_v1.3.xsd). • tva_metadata_3-1.xsd - TV-Anytime schema (imported into dvbhb-extensions_v1.3.xsd and dvbi_types_v1.0.xsd). • tva_mpeg7.xsd - TV-Anytime profile of MPEG-7 schema (imported into dvbhb-extensions_v1.3.xsd and dvbi_types_v1.0.xsd). • dvbi_v6.0.xsd - DVB-I service list schema (referenced in examples). • dvbi_service_list_discovery_v1.6.xsd - DVB-I service list discovery schema (referenced in examples). • avail_map_first_example.xml - Example of a ServiceAvailabilityMap XML document (see clause 7.3.3). • extended_ServiceListEntryPoints.xml - Example of ServiceListEntryPoints published by a DVB-HB Local Server (see clause 9.2). • extended_DASH_service_instance.xml - Example of DASH service instance published by a DVB-HB Local Server (see clause 9.3). • nownext.xml - Example of result of a query to the Content Guide server for present/following (see clause 10.3). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 64 Annex C (informative): Examples of ServiceAvailabilityMap.xml for different use cases C.1 One shared tuner C.1.1 Exclusive assignment of the tuner resources Pseudocode C.1 shows an example of a Service Availability Map describing one single tuner with exclusive transcoding, no sharing. Pseudocode C.1: One single tuner with exclusive transcoding, no sharing <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="false" totalServedClients="1" totalServedClientsMax="1" totalTranscoded Clients="1" totalTranscodedClientsMax="1" totalTranscodedServicesMax="1"> <DependencyResourceGroup id="tuner" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="1"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> This is the simplest case where a DVB-HB Local Server assigns its single tuner to one single DVB-HB Client. Assuming here that client A is receiving "Das Erste" service, in <HBLocalServerNode> element, the value of @totalServedClients has reached the maximum value, so no further services can be assigned to other clients. Since client A is using "Das Erste", releasing this resource would set the @used attribute on the service to 0. As the @used attribute is set to 0, also the @used attribute of <DependencyResourceGroup> element above would be set to 0 and the @totalServedClients attribute would be set to 0. This means that a new client could now offer any of the services again. Table C.1 shows the result in terms of available services in the situation of pseudocode C.1. Table C.1: Available services (one single tuner with exclusive transcoding) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y Y Y Y Y B - N N N N N C - N N N N N D - N N N N N E - N N N N N F - N N N N N G - N N N N N H - N N N N N Pseudocode C.2 shows the same example in a case where transcoded is disabled. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 65 Pseudocode C.2: One single tuner, no transcoding, no sharing <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="false" totalServedClients="1" totalServedClientsMax="1" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> C.1.2 One tuner in shared mode with up to 3 clients served C.1.2.1 Case 1: All clients on one service - single service per multiplex Pseudocode C.3 shows an example of a Service Availability Map describing one shared single tuner used by three clients, with no transcoding. Pseudocode C.3: One shared single tuner used by three clients with no transcoding <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="50" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner" max="1" used="1"> <DependencyResourceGroup id="mux1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="3" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Compared with the example in clause C.1.1, the tuner can be shared amongst the DVB-HB Clients on the LAN. Here it is relevant to create <DependencyResourceGroup> elements to describe multiplexes. Assuming that clients A, B and C are on "Das Erste" belonging to Mux1, i.e. a multiplex carrying a single service, in this case any additional client can only access "Das Erste" service belonging to Mux1, so there is no benefit with respect to the example in clause C.1.1. Table C.2 shows the result in terms of available services in the situation of pseudocode C.3. Table C.2: Available services (one shared single tuner used by three clients, no transcoding) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y N N N N B "Das Erste" Y N N N N C "Das Erste" Y N N N N D - Y N N N N E - Y N N N N F - Y N N N N G - Y N N N N H - Y N N N N ETSI ETSI TS 104 025 V1.1.1 (2024-07) 66 As only one tuner is available, other services can be accessed only after all clients A, B and C release the resource. A variant with exclusive transcoding is shown in pseudocode C.4. Here there are three independent transcoders used by three clients; additional clients could access "Das Erste" but only in non-transcoded mode. Pseudocode C.4: One shared single tuner used by three clients with exclusive transcoding <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="50" totalTranscoded Clients="3" totalTranscodedClientsMax="3" totalTranscodedServicesMax="3"> <DependencyResourceGroup id="tuner" max="1" used="1"> <DependencyResourceGroup id="mux1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="3" transcodedUsed="3"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Finally, pseudocode C.5 shows the same example where two clients are using exclusive transcoding, while a third one is using in a shared mode. One additional client could access "Das Erste" in shared transcoded mode (Profile B). Pseudocode C.5: One shared single tuner used by three clients with partially exclusive transcoding <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="50" totalTranscoded Clients="2" totalTranscodedClientsMax="3" totalTranscodedServicesMax="3"> <DependencyResourceGroup id="tuner" max="1" used="1"> <DependencyResourceGroup id="mux1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="3" transcodedUsed="2"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> C.1.2.2 Case 2: All clients on one service - multiple services per multiplex Pseudocode C.6 also shows an example of a Service Availability Map describing one shared tuner used by three clients, but, with respect to the example in clause C.1.2.1, the selected service is not the only one in the multiplex. Pseudocode C.6: One shared tuner used by three clients, multiple services per multiplex <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="4" totaltranscodedC lients="0" totalTranscodedClientsMax="3" totalTranscodedServicesMax="3"> <DependencyResourceGroup id="tuner" max="1" used="0"> <DependencyResourceGroup id="mux1" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="1"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="3" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 67 <DependencyResourceGroup id="mux3" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Here, assuming that clients A, B and C are on "ZDF" belonging to Mux2, additional clients can access services also belonging to Mux2, i.e. "ZDF" or "3SAT" in this case. In this example, transcoding is available but not used. Table C.3 shows the result in terms of available services in the situation of pseudocode C.6. Table C.3: Available services (one shared tuner used by three clients, multiple services per multiplex) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "ZDF" N Y Y N N B "ZDF" N Y Y N N C "ZDF" N Y Y N N D - N Y Y N N E - N Y Y N N F - N Y Y N N G - N Y Y N N H - N Y Y N N C.2 Two independent tuners C.2.1 Exclusive assignment of the tuner resources Pseudocode C.7 shows an example of a Service Availability Map describing two tuners with service exclusive assignment of the tuner, no transcoding enabled. In this representation, two <DependencyResourceGroup> elements are defined, one per tuner. Pseudocode C.8 shows the same example with an alternative equivalent representation, with only one <DependencyResourceGroup> element defined, merging the two tuners (i.e. @max attribute is set to 2). Pseudocode C.7: Two tuners with exclusive assignment, no transcoding (first representation) <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="false" totalServedClients="2" totalServedClientsMax="2" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 68 Pseudocode C.8: Two tuners with exclusive assignment, no transcoding (alternative representation) <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="false" totalServedClients="2" totalServedClientsMax="2" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner" max="2" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> In this example, the DVB-HB Local Server has two independent tuners which can receive all the services, e.g.: • Two DVB-T/DVB-T2 tuners. • Two DVB-S/DVB-S2/DVB-S2X tuners, each with a dedicated LNB feed. • One DVB-T/DVB-T2 tuner and one DVB-S/DVB-S2/DVB-S2X tuner (assuming that the same services are delivered on terrestrial and satellite networks). • Etc. Each tuner can only select one service, irrespective of whether on the same or different multiplex. Transcoding is disabled. Here client A is served with "Das Erste" on tuner1 on an exclusive basis. There is still one tuner completely available, so other clients may use tuner2 to access any service. If client A releases "Das Erste", tuner1 would be completely available again (i.e. @used attribute set to 0). Table C.4 shows the result in terms of available services in the situation of pseudocode C.7. Table C.4: Available services (two tuners with exclusive assignment) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "ZDF" Y Y Y Y Y B - Y Y Y Y Y C - Y Y Y Y Y D - Y Y Y Y Y E - Y Y Y Y Y F - Y Y Y Y Y G - Y Y Y Y Y H - Y Y Y Y Y C.2.2 Two independent tuners in shared mode receiving all services - one service at a time C.2.2.1 Case 1: Spare resources on one service Pseudocode C.9 shows an example of a Service Availability Map describing two tuners with sharing capabilities, in a case where spare resources on a service are still available. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 69 Pseudocode C.9: Two tuners with sharing capabilities, spare resources on a service still available <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="50" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="2" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="1" transcodedUsed="0"/> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> The DVB-HB Local Server has two independent tuners which can receive all the services. Transcoding is disabled. Each tuner can serve several clients (i.e. @shared attribute is set to true), but only one service per tuner at a time. One service may be served to several clients at the same time. Here clients A and B are receiving "Das Erste" on tuner1, while client C is receiving "SAT.1" on tuner2. Any client can be served with "Das Erste" or "SAT.1" in shared mode. Moreover, client C can be served with any service, as tuner2 is currently not shared with other clients. Table C.5 shows the result in terms of available services in the situation of pseudocode C.9. Table C.5: Available services (two tuners with sharing capabilities, spare resources still available) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y N N N Y B "Das Erste" Y N N N Y C "SAT.1" Y Y Y Y Y D - Y N N N Y E - Y N N N Y F - Y N N N Y G - Y N N N Y H - Y N N N Y C.2.2.2 Case 2: No spare exclusive transcoding resources on one service Pseudocode C.10 shows an example of a Service Availability Map describing two tuners with sharing capabilities, in a case where no spare exclusive transcoding resources are still available. Pseudocode C.10: Two tuners with sharing capabilities, no spare exclusive transcoding resources available <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="3" totalServedClientsMax="50" totalTranscoded Clients="3" totalTranscodedClientsMax="3" totalTranscodedServicesMax="3"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="2" transcodedUsed="2"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="1" transcodedUsed="1"/> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 70 </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Compared with the example in clause C.2.2.1, three clients use exclusive transcoding, client A and client B for "Das Erste" service on tuner1, client C for "SAT.1" service on tuner2, so additional clients could offer "SAT.1" or "Das Erste" only in non-transcoded mode. Table C.6 shows the result in the situation of pseudocode C.10 for non-transcoded available services, while table C.7 shows the result for transcoded available services. Table C.6: Non-transcoded available services (two tuners with sharing capabilities, no exclusive transcoding spare resources available) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y N N N Y B "Das Erste" Y N N N Y C "SAT.1" Y Y Y Y Y D - Y N N N Y E - Y N N N Y F - Y N N N Y G - Y N N N Y H - Y N N N Y Table C.7: Transcoded available services (two tuners with sharing capabilities, no exclusive transcoding spare resources available) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y N N N Y B "Das Erste" Y N N N Y C "SAT.1" Y Y Y Y Y D - N N N N N E - N N N N N F - N N N N N G - N N N N N H - N N N N N C.2.3 Two independent tuners in shared mode receiving all services - multiple services per multiplex Pseudocode C.11 shows an example of a Service Availability Map describing two tuners with sharing capabilities, which can serve multiple services if they are carried in the same multiplex. Transcoding is not available. Pseudocode C.11: Two tuners with sharing capabilities, multiple services per multiplex <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="2" totalServedClientsMax="50" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <DependencyResourceGroup id="mux1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="1" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="1"> <DependencyResourceGroup id="mux1" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:daserste.ses.com" used="0" transcodedUsed="0"/> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 71 </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="1"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Table C.8 shows the result in terms of available services in the situation of pseudocode C.11. Table C.8: Available services (two tuners with sharing capabilities, multiple services per multiplex) Client Current service "Das Erste" "ZDF" "3SAT" "RTL" "SAT.1" A "Das Erste" Y Y Y Y Y B "ZDF" Y Y Y Y Y C - Y Y Y N N D - Y Y Y N N E - Y Y Y N N F - Y Y Y N N G - Y Y Y N N H - Y Y Y N N C.2.4 Two tuners in shared mode with daisy-chained LNB Pseudocode C.12 shows an example of a Service Availability Map describing a special case with multiple tuners connected to a daisy-chained LNB. In this case, though several multiplexes can be received at the same time through the daisy chain, only one polarization and band can be received at a time, which means that only one quarter of the services are available at the same time (in the example, only multiplexes belonging to polbamd1 can be served). Pseudocode C.12: Two tuners in shared mode with daisy-chained LNB <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="2" totalServedClientsMax="50" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="LNB" max="1" used="1"> <DependencyResourceGroup id="polband1" max="2" used="2"> <DependencyResourceGroup id="mux1" max="1" used="1"> <Service serviceRef="tag:ses.com,2024;daserste.ses.com" used="3" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="2" used="2"> <Service serviceRef="tag:ses.com,2024;zdf.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024;3sat.ses.com" used="1" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="polband2" max="2" used="0"> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024;DMAX.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024;Tele5.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="polband3" max="1" used="0"> <DependencyResourceGroup id="mux5" max="1" used="0"> <Service serviceRef="tag:ses.com,2024;MainFrankenHD.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="polband4" max="2" used="0"> <DependencyResourceGroup id="mux6" max="1" used="0"> <Service serviceRef="tag:ses.com,2024;RTL.ses.com" max="3" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux7" max="1" used="0"> <Service serviceRef="tag:ses.com,2024;SAT.1.ses.com" max="3" used="0" transcodedUsed="0"/> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 72 </DependencyResourceGroup> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Table C.9 shows the result in terms of available services in the situation of pseudocode C.12. Table C.9: Available services (two tuners in shared mode with daisy-chained LNB) Client Current service "Das Erste" "ZDF" "3SAT" "DMAX" "Tele5" "MainFr." "RTL" "SAT.1" A "Das Erste" Y Y Y N N N N N B "Das Erste" Y Y Y N N N N N C "Das Erste" Y Y Y N N N N N D "ZDF" Y Y Y N N N N N E "3SAT" Y Y Y N N N N N F - Y Y Y N N N N N G - Y Y Y N N N N N H - Y Y Y N N N N N C.3 Four independent tuners Pseudocode C.13 shows an example of a Service Availability Map describing four independent tuners in shared mode receiving all services, with multiple services per multiplex at a time. Pseudocode C.13: Four independent tuners <ServiceAvailabilityMap version="2005201628" > <HBLocalServerNode shared="true" totalServedClients="6" totalServedClientsMax="50" totalTranscoded Clients="0" totalTranscodedClientsMax="0" totalTranscodedServicesMax="0"> <DependencyResourceGroup id="tuner1" max="1" used="1"> <DependencyResourceGroup id="mux1" max="3" used="1"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="1" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:hse24.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux5" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:tv5monde.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="tuner2" max="1" used="1"> <DependencyResourceGroup id="mux1" max="3" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="2" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:hse24.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux5" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:tv5monde.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="tuner3" max="1" used="1"> <DependencyResourceGroup id="mux1" max="3" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> ETSI ETSI TS 104 025 V1.1.1 (2024-07) 73 <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="2" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:hse24.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux5" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:tv5monde.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> <DependencyResourceGroup id="tuner4" max="1" used="1"> <DependencyResourceGroup id="mux1" max="3" used="0"> <Service serviceRef="tag:ses.com,2024:zdf.ses.com" used="0" transcodedUsed="0"/> <Service serviceRef="tag:ses.com,2024:3sat.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux2" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:RTL.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux3" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:SAT.1.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux4" max="1" used="1"> <Service serviceRef="tag:ses.com,2024:hse24.ses.com" used="1" transcodedUsed="0"/> </DependencyResourceGroup> <DependencyResourceGroup id="mux5" max="1" used="0"> <Service serviceRef="tag:ses.com,2024:tv5monde.ses.com" used="0" transcodedUsed="0"/> </DependencyResourceGroup> </DependencyResourceGroup> </HBLocalServerNode> </ServiceAvailabilityMap> Table C.10 shows the result in terms of available services in the situation of pseudocode C.13. Table C.10: Available services (four independent tuners) Client Current service "ZDF" "3SAT" "RTL" "SAT.1" "HSE24" "TV5Monde" A "ZDF" Y Y Y Y Y Y B "RTL" Y Y Y Y Y N C "RTL" Y Y Y Y Y N D "SAT.1"" Y Y Y Y Y N E "SAT.1"" Y Y Y Y Y N F "HSE24" Y Y Y Y Y Y G - Y Y Y Y Y N H - Y Y Y Y Y N ETSI ETSI TS 104 025 V1.1.1 (2024-07) 74 Annex D (informative): Provision of HbbTV applications to DVB-HB Clients D.1 Use case HbbTV® applications can be delivered to clients either via IP over the Internet, or within the broadcast TS as a DSM- CC carousel. The DSM-CC option may be preferred in some cases, e.g. for privacy reasons (i.e. the application asks permissions to establish communication with the broadcaster's server before accessing the Internet URL), or when targeting devices not connected to the Internet (i.e. the application provides some Teletext-like information for non-connected devices). In the context of DVB-HB, the target device could be a TV/STB with HbbTV® and DVB-I capabilities, or a PC/Tablet/STB running an application implementing HbbTV® browsing and DVB-I. D.2 Implementation in Profile A In case of Profile A this is natively covered, i.e. the DVB-HB Client can request all necessary TS PIDs in its RTSP request, and will then take care of decoding the DSM-CC packets. D.3 Implementation in Profile B D.3.1 General In case of Profile B, provision of HbbTV® applications to DVB-HB Clients can be achieved by leveraging specifications ETSI TS 103 770 [3] and ETSI TS 102 809 [19]. If the HbbTV® application is delivered via IP over the Internet, the DVB-HB Local Server has the task of signalling its public URL. If the HbbTV® application is transported as a DSM-CC carousel, it is a task of the DVB-HB Local Server (namely, the Content preparation function in the DVB-HB reference architecture, see clause 5) to extract the original HbbTV® application (i.e. files with path) from the DSM-CC carousel carried in the incoming TS (this task is natively supported if the DVB-HB Local Server is implemented on an HbbTV®-enabled TV or STB), and to keep it up-to-date in case of variations in the data carousel, and to deliver it on the LAN to the DVB-HB Clients as an HTTP session. D.3.2 Signalling The original AIT, present in the incoming TS and associated in the Program Map Table (PMT) with the selected service, can be converted into an XML-based AIT by the DVB-HB Local Server, as defined in ETSI TS 102 809 [19], clause 5.4: • If the HbbTV® application is delivered via IP over the Internet, the XML-based AIT references the public URL of the application files; • If the HbbTV® application is transported as a DSM-CC carousel, the XML-based AIT references the local URL of the extracted application files, hosted on the DVB-HB Local Server (see also clause D.3.3). In both cases, the generated XML-based AIT can be signalled in the DVB-I Service List published by the DVB-HB Local Server as a linked application as described in ETSI TS 103 770 [3]. An example is shown in pseudocode D.1. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 75 Pseudocode D.1: Example of a service associated with a linked HbbTV® application <Service version="1"> <UniqueIdentifier>tag:192.168.1.101,2024:Service1+HbbTV</UniqueIdentifier> <ServiceInstance> <DASHDeliveryParameters> <UriBasedLocation contentType="application/dash+xml"> <dvbi-types:URI>http://192.168.1.101/dvbhb/dash/Service1+HbbTV.mpd</dvbi-types:URI> </UriBasedLocation> </DASHDeliveryParameters> </ServiceInstance> <ServiceName>Service1+HbbTV</ServiceName> <ProviderName>Broadcaster 1</ProviderName> <RelatedMaterial> <tva:HowRelated href="urn:dvb:metadata:cs:LinkedApplicationCS:2019:1.1"/> <tva:MediaLocator> <tva:MediaUri contentType="application/vnd.dvb.ait+xml"> http://192.168.1.101/dvbhb/hbbtv/Service1+HbbTV.aitx </tva:MediaUri> </tva:MediaLocator> </RelatedMaterial> </Service> NOTE 1: This solution also supports dynamic AITs, provided that the DVB-HB Local Server either updates the DVB-I Service List coherently, or uses the signalling carried by a DVB-DASH EventStream as described in ETSI TS 103 770 [3], clause 5.2.3.3. NOTE 2: This solution is applicable to applications that use relative URLs (i.e. relative to the first page of the application as signalled), while it is not applicable to applications that use dvb:URLs explicitly. NOTE 3: If the DVB-HB Local Server has knowledge that the DVB-HB Clients do not have access to the Internet, it may include in the XML-based AIT only HbbTV® applications transported as a DSM-CC carousel, for a better Quality of Service (QoS). D.3.3 Data delivery If the HbbTV® application is transported as a DSM-CC carousel, the HbbTV® files, after being extracted by the DVB-HB Local Server, can be exposed by its HTTP server (i.e. the Content publication function in the DVB-HB reference architecture, see clause 5). Such files can be retrieved on request (i.e. pulled) and decoded by a DVB-HB Client implementing the HbbTV® stack. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 76 Annex E (informative): Background information on resilience in Wi-Fi networks E.1 Introduction TV services redistributed on the LAN 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. Some studies exist about measuring the reliability of Wi-Fi networks based on the IEEE 802.11 [i.15] family. Some of them also consider video distribution in broadcast over Wi-Fi, where MAC level retransmissions are not applicable [i.16] and [i.17]. The present document, in clause 8.4.2, specifies an optional AL-FEC mechanism, implemented on top of IEEE 802.11 [i.15] technologies, improving network resilience. Here, an introduction of packet loss models and packet loss reduction techniques available in modern Wi-Fi implementations based on IEEE 802.11 [i.15] standards is provided for information. NOTE: It is acknowledged that, at the time of writing, some amendments that significantly improve the IEEE 802.11 [i.15] physical layer and radio chains have already been defined (e.g. 802.11ax) or are under development by 802.11 task groups. Therefore, some of the possible issues presented in the present document may not be applicable, or be applicable with a lesser degree, to newer Wi-Fi network implementations. Nevertheless, in order to be backwards compatible with older devices and current off- the-shelf devices, the content of this clause is still fully relevant in the DVB-HB scenario. E.2 Packet loss models While the first packet loss models that can be found in literature focused only on errors at the physical layer, in reality packets can be lost for many reasons, including issues at the data link layer (MAC). Packet loss causes can be classified as follows [i.18]: • Physical layer: - Interference (hidden terminal, hidden node) - Co-existence (Wi-Fi, other wireless services) - Fading (multipath effect, weak signal, hand-off / hand-over) • MAC layer: - Collisions (competition medium, hidden terminals) - Buffer loss (insufficient memory, bufferbloat) Collisions and buffer losses are, most likely, the main packet loss reasons in the DVB-HB scenario [i.16] and [i.18]. Regarding the distribution of the losses, it is generally acknowledged that, for Wi-Fi networks, burst losses are the most common kind [i.18] and [i.19]. For video streaming purposes, burst losses generally produce a larger total distortion than an equal number of isolated losses and, in [i.19], the authors proposed a model for estimating video distortion related to the specific loss pattern. The model is proved to be valid for general and complex loss patterns, including burst losses and separate, non-consecutive losses. NOTE: Burst losses are less pronounced for high bit-rate video streams rather than for low bit-rates. The reason for this is because in high bit-rate video streams each frame is encoded in multiple packets, requiring therefore much longer bursts to have similar effects [i.20]. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 77 Generally speaking, Markov Chains with multiple states and variable length burst losses are the dominant strategy for modelling Wi-Fi packet loss [i.18] and [i.21]. Two-states Markov/Gilbert-Elliot models are also very popular due to their simplicity [i.22]. E.3 Packet loss reduction techniques E.3.1 Introduction As discussed in clause E.2, packet losses can be quite frequent in wireless networks. In this clause some solutions that can improve network robustness and resilience in order to deliver video streams with the appropriate Quality of Experience (QoE)/QoS, specifically tailored to IEEE 802.11 [i.15] networks, are presented. NOTE: Some of the solutions proposed in this clause may not be implemented in a standardized fashion or in Commercial Off-The-Shelf (COTS) wireless devices. E.3.2 FEC/ARQ vs. AL-FEC The Wi-Fi standards of the IEEE 802.11 [i.15] family inherently use FEC at the physical layer and Automatic Repeat reQuest (ARQ) at the link layer to reduce residual packet losses to a minimum [i.22] and prevent packet losses from being recovered by TCP, when used (i.e. losses that are not recovered by FEC/ARQ at link layer are interpreted by TCP as congestion) [i.16]. The FEC schemes used by IEEE 802.11 [i.15] amendments up to date are typically convolutional codes with short constraint lengths, Viterbi maximum-likelihood decoders and variable coding rates, depending on the Modulation and Coding Scheme (MCS) value used at the physical layer for the transmission [i.23]. While the use of FEC is essential for throughput and time-critical applications such as video streaming, the use of simple ARQ schemes might not always be feasible due to the strict time requirements. In [i.24] the authors developed a model based on the assumption that the main packet loss causes are congestion and wireless channel losses and evaluated the performance gain in terms of Playable Frame Rate (PFR) when using different FEC overhead values (i.e. for standard IEEE 802.11 [i.15] FEC convolutional codes and ARQ with a given maximum number of retransmissions). Results show that the use of FEC with the right amount of overhead might be enough to guarantee a proper playback rate. NOTE: Higher values of FEC overhead can stress the network and cause congestion. In real-world IEEE 802.11 [i.15] networks, FEC overhead values have been found to vary between 5 % and 45 %. In applications where connectionless RTP/UDP streams are employed and retransmissions are not allowed, AL-FEC is a solution which is often recommended in video streaming applications over Wi-Fi [i.17]. E.3.3 Adaptive Cross-layer FEC In traditional implementations, the FEC function is either implemented at bit-level in the physical layer (e.g. standard IEEE 802.11 [i.15] behaviour) or at the packet-level in the application layer (i.e. AL-FEC). The redundancy introduced by the FEC can be either static or dynamic (i.e. determined by the radio MCS parameters or controlled by the application-layer programs). When dynamic/adaptive AL-FEC is used, the redundancy rate is determined using the information coming from the lower Open Systems Interconnection (OSI) layers. This information, though, may not capture real-time network conditions with sufficient accuracy due to transmission delay and network congestion, resulting in an inefficient packets recovery for time-sensitive applications like video streaming. In [i.22] the authors proposed a mechanism based on Adaptive Cross-layer Forward Error Correction (ACFEC) to be implemented in the Wi-Fi Access Point (AP). In this way, using the information provided by the AP, it is possible to monitor traffic flows and capture varying channel conditions in real-time, so that the source node can adapt the FEC rate accordingly. The proposed solution targets specifically blocks of video data packets and monitors their transmission status and any eventual failure using ARQ at the MAC layer, in cooperation with UDP protocol at the transport layer. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 78 The solution has been tested using an encoded video sequence, encapsulated in RTP/UDP/IP packets and sent over the WLAN. Simulation results in a network with normal traffic conditions are provided, comparing the performance of ACFEC with static FEC, in terms of number of FEC packets and video Peak Signal to Noise Ratio (PSNR) as a function of the packet loss rate [i.22]. E.3.4 More efficient ARQ techniques ARQ is a mechanism used to trigger retransmissions of lost packets and conduct data transfer in a reliable way. A retransmission can be triggered in two ways: upon request from the receiver and upon expired timeout of the timer from the sender [i.22]. As mentioned earlier, a traditional ARQ mechanism might not always be applicable for video streaming due to delay and timing constraints imposed by the decoding operations [i.22]. As a result, a consistent number of alternative ARQ schemes have been proposed during the years to target this use-case. The following is a non-exhaustive list of alternative and video related ARQ schemes: Cross-Layer Perceptual ARQ ARQ is performed at the application layer, with retransmission opportunities evaluated on a GOP- by-GOP basis, to exploit the information about the perceptual and temporal importance of each packet [i.25]. Soft ARQ Mechanism based on legacy and delay-constrained ARQ scheme, leveraging layered encoding/transmissions and avoiding retransmitting late data that would not be useful at the decoder, with bandwidth saving. Tests of this solution in high packet loss conditions are reported in [i.26]. Conditional ARQ Retransmission and Low-Delay Interleaving Hybrid FEC/ARQ scheme, leveraging selective retransmission and video packets interleaving scheme. Selective retransmission is performed using concealment error, a prediction of the distortion introduced by the missing packet and the channel conditions. The interleaving scheme, instead, is used to convert burst errors into correctable bit-errors [i.20]. E.3.5 Other solutions Also the following solutions, among others, allow to improve resilience in Wi-Fi networks: Accurate Packet dimensioning In [i.27] the authors demonstrated the correlation between hidden traffic and packet losses by developing a new model. During their work, they proved that the packet airtime occupation is an important factor in the trade-off between protocol efficiency (i.e. payload time over total time) and the losses related to hidden nodes in the network. Therefore, they derived the optimal frame length to be used in case of hidden nodes in a closed form and backed up the results with network simulations. Multipath Video Streaming An emerging trend in high-quality video streaming is the use of multipath transmissions to tackle the limitations imposed by bandwidth, timing and packet loss constraints. It has been proved by multiple sources that multipath transmissions can lead to substantial performance gains in wireless networks with severe burst-loss rates [i.28]. Moreover, this approach inherently increases bandwidth, network resilience and load balancing of WLAN networks. NOTE: Smartphones and other hand-held devices may have a single IEEE 802.11 [i.15] radio chain (i.e. 1x1) and, therefore, cannot benefit from a multipath approach. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 79 Annex F (informative): Implementation aspects F.1 Introduction This Annex presents additional considerations and suggestions relevant to some implementation aspects, complementing the specific implementation aspects or deployment models already included in various clauses of the present document. F.2 Exposure of a single or multiple Service Lists As specified in clause 7.2, clause 8.3 and clause 9.2, a DVB-HB Local Server exposes basic information about itself either in the form of an extended "XML Device Description" as defined in EN 50585 [1] (Profile A), or of an extended Service List Entry Points XML document as defined in ETSI TS 103 770 [3] (Profile B; an example is given in pseudocode 14). In both cases, one or multiple Service Lists can be referenced as part of such information and exposed to DVB-HB Clients. In a typical implementation choice, a DVB-HB Local Server may expose a single Service List, including all received broadcast services; however, there may be use cases where support of multiple Service Lists is useful (e.g. in hospitality environments, providing different Service Lists to different categories of users with respect to language, or to offer premium packages, etc.). Support of multiple Service Lists adds complexity when the Service Availability Map option is implemented: in this case, with respect to the algorithm presented in clause 7.3.4, the DVB-HB Local Server should first merge all the exposed Service Lists into a single one (which may be exposed as well or hidden to clients) and then build the ServiceAvailabilityMap.xml document according to such merged list. However, the above use cases may be equally fulfilled without the need of supporting multiple Service Lists, but adopting alternative implementation options. For instance, the DVB-HB Local Server may expose a single Service List, defining multiple Target Regions or multiple Subscription Packages as allowed by ETSI TS 103 770 [3]. F.3 Releasing resources in Profile B In order to make optimal use of their resources (i.e. tuners, encoding), DVB-HB Local Servers may keep track of currently connected DVB-HB Clients, releasing resources when they are no more in use by a DVB-HB Client. While Profile A DVB-HB Clients can explicitly release DVB-HB Local Server's resources as soon as a service is no more consumed, by sending a TEARDOWN message as defined in EN 50585 [1], Profile B DVB-HB Clients, according to behaviour of legacy DVB-I Clients, do not send such explicit messages when a resource is released. A possible method for Profile B DVB-HB Local Servers to detect if a service is no more consumed by a Profile B DVB-HB Client, and therefore the associated resources can be released, is checking if HTTP GET requests [i.5] are not being received for that service within a certain timeout (e.g. 5 times the DASH segment length). However, this method would be suboptimal during channel change by a DVB-HB Client, as resources associated with the old service would not be released immediately, but only after the timeout has expired. A possible implementation improvement could be done under the assumption that DVB-HB Clients can consume only one service at a time. In this case, when a DVB-HB Local Server receives an DASH GET request for a new MPD from a certain DVB-HB Client (i.e. from a certain source IP address, or using HTTP cookies [i.29]), it can assume that the same DVB-HB Client is releasing the previously allocated resource. Figure F.1 provides a possible implementation algorithm, relevant to a DVB-HB Local Server managing unshared tuners and under the assumption that DVB-HB Clients can consume only one service at a time. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 80 Figure F.1: A possible implementation algorithm for resource lock and release in a Profile B DVB-HB Local Server with unshared tuners If such assumption cannot be made, then the DVB-HB Local Server needs at least one tuner more than the number of active DVB-HB Clients, to cope with the transient periods after channel changes, i.e. until the release timeout has expired. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 81 Annex G (informative): Change history Date Revision Information about changes 02/2021 A179 Initial version 10/2022 A179r1 XML schemas aligned to updated DVB-I specification (i.e. referencing urn:dvb:metadata:servicediscovery:2022b and urn:dvb:metadata:servicelistdiscovery:2022b), including support of <Delivery> element in Service List Discovery. Clause 11 (informative) extended with Private Network Access concept. New informative Annex F (Implementation aspects). References to obsolete IETF RFC documents updated. 07/2023 A179r2 Added discovery mechanism based on mDNS/DNS-SD (clause 6.3.5), aligned with DVB- NIP. Improved optional discovery mechanism based on UPnP (clause 6.3.2) and added examples. XML schemas aligned to updated DVB-I specification (i.e. referencing urn:dvb:metadata:servicediscovery:2023 and urn:dvb:metadata:servicelistdiscovery:2023). 02/2024 ETSI TS 104 025 V0.0.1 XML schemas aligned to updated DVB-I specification (ETSI TS 103 770 V1.2.1), i.e. referencing only urn:dvb:metadata:servicediscovery-types:2023. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 82 History Document history V1.1.1 July 2024 Publication |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 1 Scope | The present document specifies the management plane protocols used over the fronthaul interface linking the O-RAN Radio Unit (O-RU) with other management plane entities, that may include the O-RAN Distributed Unit (O-DU), the O-RAN defined Service Management and Orchestration (SMO) functionality as well as other generic Network Management Systems (NMS). |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 2 References | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] Void. [2] ETSI TS 103 859 (V17.1.0): "Publicly Available Specification (PAS); O-RAN Fronthaul Control, User and Synchronization Plane Specification v17.01 (O-RAN.WG4.TS.CUS.0-R004-v17.01)". [3] IETF RFC 6241: "Network Configuration Protocol (NETCONF)". [4] IETF RFC 7950: "The YANG 1.1 Data Modeling Language". [5] IETF RFC 6242: "Using the NETCONF Protocol over Secure Shell (SSH)". [6] IETF RFC 4252: "The Secure Shell (SSH) Authentication Protocol". [7] IETF RFC 4253: "The Secure Shell (SSH) Transport Layer Protocol". [8] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions". [9] IETF RFC 3925: "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)". [10] IETF RFC 2131: "Dynamic Host Configuration Protocol". [11] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". [12] Void. [13] Void. [14] Void. [15] IETF RFC 8071: "NETCONF Call Home and RESTCONF Call Home". [16] Small Form Factor Committee SFF-8472: "Management Interface for SFP+". [17] Void. [18] IETF RFC 862: "Echo Protocol". [19] Void. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 13 [20] Void. [21] IETF RFC 5277: "NETCONF Event Notifications". [22] Recommendation ITU-T G.8275.1 (2022): "Precision time protocol telecom profile for phase/time synchronization with full timing support from the network". [23] Recommendation ITU-T G.810 (1996): "Definitions and terminology for synchronization networks". [24] IEEE 1588™-2008: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". [25] Recommendation ITU-T Y.1731 (2023): "Operation, administration and maintenance (OAM) functions and mechanisms for Ethernet based networks". [26] Antenna Interface Standards Group AISG 2.0 (2006): "Control interface for antenna line devices". [27] ETSI TS 137 462 (V15.2.0): "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Iuant interface: Signalling transport (3GPP TS 37.462 version 15.2.0 Release 15)". [28] ETSI TS 137 466 (V15.5.0): "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Iuant interface: Application part (3GPP TS 37.466 version 15.5.0 Release 15)". [29] Void. [30] Recommendation ITU-T X.733 (1992): "Information Technology - Open Systems Interconnection - System Management: Alarm Reporting Function". [31] IETF RFC 6187: "X.509v3 Certificates for Secure Shell Authentication". [32] ETSI TS 136 213 (V13.6.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (3GPP TS 36.213 version 13.6.0 Release 13)". [33] IETF RFC 4361: "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)". [34] Small Form Factor Committee SFF-8636: "Management Interface for 4-lane Modules and Cables". [35] IETF RFC 6470: "Network Configuration Protocol (NETCONF) Base Notifications". [36] Void. [37] IETF RFC 8639: "Subscription to YANG Notifications". [38] IETF RFC 7951: "JSON Encoding of Data Modeled with YANG". [39] Void. [40] Void. [41] IETF RFC 7589: "Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication", IETF, June 2015. [42] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". [43] Void. [44] IETF RFC 4210: "Internet X.509 Public Key Infrastructure Certificate Management Protocol". [45] IANA: "Transport Layer Security (TLS) Parameters". [46] ETSI TS 133 210: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210)". ETSI ETSI TS 104 023 V17.1.0 (2026-01) 14 [47] Void. [48] Void. [49] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". [50] IEEE Std 1588™-2019: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". [51] ETSI TS 133 310: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310)". [52] ETSI TS 132 509: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network (3GPP TS 32.509)". [53] Void. [54] IETF RFC 4217: "Securing FTP with TLS". [55] Void. [56] O-RAN ALLIANCE O-RAN.WG11.Security-Protocols-Specification.O: "Security Protocols Specifications". [57] ETSI TS 128 552: "5G; Management and orchestration; 5G performance measurements (3GPP TS 28.552)". [58] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". [59] IETF RFC 8525: "YANG Library". [60] ETSI TS 128 532: "5G; Management and orchestration; Generic management services (3GPP TS 28.532)". [61] IETF RFC 4191: "Default Router Preferences and More-Specific Routes". [62] IETF RFC 3442: "The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4". [63] IETF RFC 5656: "Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer". [64] IETF RFC 8341: "Network Configuration Access Control Model". [65] ISO/IEC 13239:2002: "Information technology — Telecommunications and information exchange between systems — High-level data link control (HDLC) procedures". [66] ETSI TS 138 104: "5G; NR; Base Station (BS) radio transmission and reception (3GPP TS 38.104)". [67] IETF RFC 6022: "YANG Module for NETCONF Monitoring". [68] IETF RFC 8332: "Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol". [69] IEEE 802.1Q™-2018: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks". [70] IEEE 802.1X™-2020: "IEEE Standard for Local and Metropolitan Area Networks--Port Based Access Control". [71] Void. [72] ETSI TS 128 316: "5G; Management and orchestration; Plug and Connect; Data formats (3GPP TS 28.316)". ETSI ETSI TS 104 023 V17.1.0 (2026-01) 15 [73] O-RAN ALLIANCE ORAN-WG9.XPSAAS.0: "Xhaul Packet Switched Architectures and Solutions". [74] ETSI TS 136 211: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (3GPP TS 36.211)". [75] ETSI TS 138 211: "5G; NR; Physical channels and modulation (3GPP TS 38.211)". [76] Recommendation ITU-T G.8264 Amd1 (03/2018): "Distribution of timing information through packet networks". [77] Recommendation ITU-T X.731 (1992): "Information Technology - Open Systems Interconnection - System Management: State Management Function". [78] IETF RFC 3396: "Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)". [79] IETF RFC 4251: "The Secure Shell (SSH) Protocol Architecture". [80] IEEE 802.1CM™-2018: "IEEE Standard for Local and metropolitan area networks -- Time-Sensitive Networking for Fronthaul". [81] Recommendation ITU-T G.781 (2024): "Synchronization layer functions for frequency synchronization based on the physical layer". [82] ETSI TS 128 111 (V18.0.0): "5G; Fault management (3GPP TS 28.111 version 18.0.0 Release 18)". [83] ETSI TS 104 104: "Publicly Available Specification (PAS); O-RAN Security Requirements and Controls Specifications (O-RAN.WG11.SecReqSpecs-R003-v09.01)". [84] IETF RFC 9525: "Service Identity in TLS". [85] IEEE 802.1AE™-2018: "IEEE Standard for Local and Metropolitan Area Networks - Media Access Control (MAC) Security". [86] IETF RFC 9642: "A YANG Data Model for a Keystore". [87] IETF RFC 2986: "PKCS #10: Certification Request Syntax Specification Version 1.7". [88] ETSI TS 137 461 (V15.5.0): "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Iuant interface: Layer 1 (3GPP TS 37.461 version 15.5.0 Release 15)". [89] Void. [90] Recommendation ITU-T G.8275.2 (2022): "Precision time protocol telecom profile for phase/time synchronization with partial timing support from the network". |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.2] ONAP: "VES Event Listener 7.2". ETSI ETSI TS 104 023 V17.1.0 (2026-01) 16 [i.3] Metro Ethernet Forum MEF.38 (2012): "Service OAM Fault management YANG Modules". [i.4] GitHub: "An extensible YANG validator and converter in python". [i.5] IETF RFC 1635: "How to Use Anonymous FTP". [i.6] O-RAN.WG1.NESUC-R003-v02.00: "Network Energy Saving Use Cases Technical Report". [i.7] O-RAN.WG11.Certificate-Management-Framework-TR.0: "Study on Certificate Management Framework". [i.8] WINNF-15-P-0047-V1.0.0: "SAS Functional Architecture", Wireless Innovation Forum Spectrum Sharing Committee, 7 September 2015. [i.9] IEEE 1914.3™-2023: "IEEE Standard for Radio over Ethernet Encapsulations and Mappings". [i.10] IETF RFC 6933: "Entity MIB (Version 4)". [i.11] IETF RFC 4268: "Entity State MIB". [i.12] IETF RFC 3433: "Entity Sensor Management Information Base". [i.13] IETF RFC 2863: "The Interfaces Group MIB". |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 3 Definition of terms, symbols and abbreviations | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1]. Ad-Hoc O-RU Controller: O-RU controllers that are not configured by DHCP when O-RU performs M-plane transport resolution and not configured by an O-RU controller using o-ran-mplane-int YANG model NOTE: An O-RU does not perform call home to any Ad-Hoc O-RU Controller. Advanced Sleep Mode (ASM): Advanced Sleep Mode is used to achieve energy saving by disabling some fraction of the O-RU's processing for a defined or undefined period of time alarm: representation of an error or failure that requires attention or reaction by an operator or some machine. Alarms have state. Refer to [82] for definition. antenna line: connection between O-RU and antenna call home O-RU Controller: O-RU controllers that are configured by DHCP when O-RU performs M-plane transport resolution as part of start-up installation procedure or that are provisioned by an O-RU controller in o-ran-mplane- int.yang cascade mode: Mode of Shared cell which is realized by several O-RUs cascaded in chain topology Control Plane (C-Plane): refers specifically to real-time control between O-DU and O-RU, and should not be confused with the UE's control plane data layer control: Data layer control is used to achieve energy saving in the O-RU through reducing the number of data layers independent of TRX-Control deep-hibernate: O-RU operational mode used to achieve maximum energy saving by disabling all carriers. This also includes turning off the C/U/S/M Plane processing units and functions of the O-RU for a defined time period. This implies that O-RU is powered off with only the deep-hibernate timer running. DownLink (DL): data flow towards the radiating antenna (generally on the LLS interface) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 17 Event-Collector: REST server to which an O-RU supporting NON-PERSISTENT-MPLANE feature can send a JSON notification, for example PNF registration. Event-collectors are configured when O-RU performs M-plane transport resolution as part of start-up installation procedure. extended Antenna-Carrier (eAxC): data flow for a single antenna (or spatial stream) for a single carrier in a single sector. fault: (hypothesized or adjudged) cause for an error or a failure (such as system malfunctions, a defect in system design, a defect in software, or external interference). Refer to [82] for definition. FHM mode: Mode of Shared cell which is realized by FHM and several O-RUs in star topology Hierarchical O-DU: O-DU that is operated in isolation, or in concert with other O-DUs, e.g. in a shared O-RU deployment, such that the O-DU(s) is(are) solely responsible for the management of the O-RU High-PHY: those portions of the PHY processing on the O-DU side of the fronthaul interface, including FEC encode/decode, scrambling, and modulation/demodulation Hybrid O-DU: O-DU that is operated such that it shares the responsibilities for the management of the O-RU with other non-O-DU systems, e.g. SMO Lower Layer Split (LLS): logical interface between O-DU and O-RU when using a lower layer (intra-PHY based) functional split Lower Layer Split Control-plane (LLS-C): logical interface between O-DU and O-RU when using a lower layer functional split Lower Layer Split Synchronization-plane (LLS-S): logical interface between O-DU and O-RU when using a lower layer functional split Lower Layer Split User-plane (LLS-U): logical interface between O-DU and O-RU when using a lower layer functional split Low-PHY: those portions of the PHY processing on the O-RU side of the fronthaul interface, including FFT/iFFT, digital beamforming, and PRACH extraction and filtering Management Plane (M-Plane): refers to non-real-time management operations between the O-DU and the O-RU Multi O-DU O-RU: O-RU that supports the SHARED-ORU-MULTI-ODU feature Multi-Operator O-RU: O-RU that supports the SHARED-ORU-MULTI-OPERATOR and SHARED-ORU-MULTI- ODU features Network Management System (NMS): from an Open Fronthaul perspective, generic Network Management System used to support O-RU operations north-node: O-DU or connected O-RU closer to the O-DU for the O-RU EXAMPLE: The cascade O-RU#1 connected to O-RU#2 is north-node for O-RU#2, when O-DU, O-RU#1 and O-RU#2 are in cascade chain topology. The O-DU in star topology connected to an FHM is north-node for the FHM. port: end of a transport link NOTE: In most cases this is an optical port. port number: number which identifies a port (see Port) NOTE 1: In case of SFP/SFP+ port, port number value is 0 to N-1 where N is number of ports in the device. NOTE 2: Numbers 0 to N-1 are assigned to ports in order following order of labels on the device (labels for ports are not necessarily numbers starting from zero). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 18 PRACH symbol: resource in the time domain having the duration of (1/Subcarrier Spacing), following cyclic prefix (excluded) in a PRACH occasion NOTE: Cyclic prefix and one or more of such consecutive PRACH Symbols constitute a PRACH preamble or a NPRACH symbol group defined in ETSI TS 136 211 [74] and ETSI TS 138 211 [75]. O-RAN Distributed Unit (O-DU): logical node hosting PDCP/RLC/MAC/High-PHY layers based on a lower layer functional split O-RAN Radio Unit (O-RU): logical node hosting Low-PHY layer and RF processing based on a lower layer functional split NOTE: This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction). O-RU Controller: network function that is permitted to control the configuration of an O-RU NOTE: Examples of O-RU controllers include, an O-DU, a classical NMS, an O-RAN Service Management and Orchestration function, or other network automation platforms. Service Management and Orchestration (SMO) system: O-RAN defined system that is responsible for RAN domain management shared cell: operation for the same cell by several O-RUs shared cell network: network for several cascade O-RUs in a chain topology or the network for one FHM and several O-RUs in a star topology shared O-RU Host: role performed by the NETCONF client associated with the operator of a Multi-Operator O-RU who determines how the resources of a Multi-Operator O-RU are partitioned between Shared Resource Operators Shared Resource Operator: role performed by the NETCONF client associated with an operator that utilizes the carrier resources of a Multi-Operator O-RU NOTE 1: The Shared Resource Operator is allocated a Shared Resource Operator identity by the Shared O-RU Host. NOTE 2: A NETCONF client of an operator can simultaneously perform the Shared O-RU Host role and the Shared Resource Operator role. Alternatively, a NETCONF client of an operator can only perform the Shared O-RU Host role and not Shared Resource Operator role, in which case the operator corresponds to a neutral host operator. software build: consistent set of software files used for a specific radio type of a defined HW version NOTE 1: Software build is subject of versioning and maintenance. NOTE 2: Software build is contained within a software package. software package: archive delivered by an O-RU vendor NOTE: It contains one or multiple builds and can be used for one or several radio products. south-node: connected O-RU far from O-DU for the O-RU EXAMPLE: The cascade O-RU#2 connected to O-RU#1 is south-node for O-RU#1, when O-DU, O-RU#1 and O-RU#2 are in cascade chain topology. The O-RU in star topology connected to an FHM is south-node for the FHM. spatial stream: data flow on the DL associated with precoded data (may be same as layers or different if there is expansion in the precoding), and on UL associated with the number of outputs from the digital beamforming (sometimes called "beams") Synchronization Plane (S-Plane): refers to traffic between the O-RU or O-DU to a synchronization controller which is generally an IEEE-1588 Grand Master (however, Grand Master functionality may be embedded in the O-DU) Synchronization Status Message (SSM): part of Recommendations ITU-T G.781 and G.8264 standards ETSI ETSI TS 104 023 V17.1.0 (2026-01) 19 Transceiver (TRX): refers to the specific processing chain in an O-RU associated with D/A or A/D converters NOTE: Due to digital beamforming the number of TRXs may exceed the number of spatial streams, and due to analogue beamforming, the number of TRXs may be lower than the number of array elements. TRX Control: TRX control is used to achieve energy saving through disabling one or more O-RU array elements for a defined or undefined period of time Transport Endpoint: for O-RU, it is identified by an O-RU interface name, plus optional alias MAC address or optional IP address and UDP-port. For O-DU, it is identified by O-DU address and optional UDP port Up-Link (UL): data flow away from the radiating antenna (generally on the LLS interface) User Plane (U-Plane): refers to IQ sample data transferred between O-DU and O-RU Virtual Connection: connection between O-RU and O-RU controller NOTE: This connection is established by means of autodetection procedure and is supervised by supervision procedure. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 3.2 Symbols | Void. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1]. ALD Antenna Line Device ASM Advanced Sleep Mode CA Certificate Authority CA/RA Certificate Authority/Registration Authority CBRS Citizens Broadband Radio Service CCM Continuity Check Message CMP Certificate Management Protocol CRC Cyclic Redundancy Check CUS Control/User/Synchronization DHCP Dynamic Host Configuration Protocol DMTC DRS Measurement Timing Configuration DRS Discovery Reference Signal DSCP Differentiated Services Code Point EAP Extensible Authentication Protocol EAPOL EAP encapsulation over LANs FHM FrontHaul Multiplexer FPGA Field Programmable Gate Array FTPES File Transfer Protocol Explicit-mode Secure GPU Graphics Processing Unit HDLC High-level Data Link Control ISS (MAC layer) Internal Sublayer Service KaY Key Agreement Entity LAA Licensed Assisted Access LBM Loop-Back Message LBR Loop Back Reply LBT Listen Before Talk LLS-M Lower Layer Split Management plane MACsec Media Access Control security ME Maintenance Entity MEP Maintenance association End Point MKA MACsec Key Agreement ETSI ETSI TS 104 023 V17.1.0 (2026-01) 20 MSS Maximum Segment Size NAT Network Address Translation NDM Non-Delay Managed NETCONF NETwork CONFiguration Protocol O-DU O-RAN Distributed Unit NOTE: See clause 3.1. O-RU O-RAN Radio Unit PAE Port Access Entity PLFS Physical Layer Frequency Synchronization PNF Physical Network Function RET Remote Electrical Tilt RPC Remote Procedure Call SAS Spectrum Access Service SecTAG MAC Security TAG SecY MAC Security Entity SFP Small Form-factor Pluggable sFTP secure File Transfer Protocol or SSH File Transfer Protocol SLAAC StateLess Address Auto Configuration SMO Service Management and Orchestration SRS Sounding Reference Signal SSH Secure Shell TEC ThermoElectric Cooler TLS Transport Layer Security TRX Transceiver T-TSC Telecom Time Subordinate Clock NOTE: This is what ITU-T standards refer to as a Telecom Time Slave Clock. VLAN Virtual LAN YANG Yet Another Next Generation |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 4 General | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 4.1 Conventions | This management plane specification includes cross references to a set of associated YANG models. Text may reference particular YANG leafs, notifications and Remote Procedure Calls (RPCs). In order to assist in readability, all cross references to YANG defined elements will keep the identical case format as defined in the corresponding YANG model, with the font-weight set to bold. This convention applies only to text and not to YANG elements embedded into figures. If there is any conflict between the YANG models and the accompanying text description in the present document, the definition of the YANG models shall take precedence. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 4.2 Void | ETSI ETSI TS 104 023 V17.1.0 (2026-01) 21 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 4.3 Revision and compatibility handling | The revision statement in the YANG models shall be used to describe future revisions to the models that are backwards compatible, where backwards compatibility changes follow the rules specified in IETF RFC 7950 [4], clause 11. The format of the namespace used in all O-RAN YANG models is "urn:o-ran:"<model-name>" :"<model-number>, where the initial <model-number> used in a newly defined YANG model is "1.0". Where the present document makes reference to models, irrespective of their backward compatibility, a generic <model-number> of "x.y" is used to enable reference to all versions of the namespace for a particular <model-name>. Backwards incompatible changes shall be addressed by incrementing the number used as part of the model name and namespace and updating the name of the model, effectively creating a new YANG model. Any backwards incompatible change to a model will change the model name from <original-model-name>.yang to <original-model-name>"x".yang, where the value "x" in the model name matches the value of "x" used in the namespace. For example, the first backwards incompatible change to o-ran- ald.yang will be included in the model named o-ran-ald2.yang and a subsequent backwards incompatible change to o-ran-ald2.yang will be included in the model named o-ran-ald3.yang. The revision statement in all YANG models shall include a reference statement used to cross-reference to the first version of the present document where the corresponding description was introduced. For example, the reference in all revision statements for the initial O-RAN models include cross-reference to "ORAN-WG4.MP.0-v01.00". The revision statement of the YANG models shall also include a description which is used to track the versioning of the YANG model. All revision statement descriptions begin with "version "<a>"."<b>"."<c>", where <a>, <b> and <c> are used to reflect the version of the YANG model, where: <a> corresponds to the first digit of the O-RAN WG4 management plane specification version where the corresponding description was first introduced, corresponding to <x> in clause 1. <b> is incremented when errors in the YANG model have been corrected. <c> is incremented only in working versions of the YANG model indicating incremental changes during the editing process. An O-RU shall use the supported-mplane-version leaf in o-ran-operations YANG model to provide the highest version of the O-RAN.WG4.MP.0 specification that the O-RU is compliant with. An O-RU declaring compliance to a version shall ensure that when its YANG library contains a YANG model listed in Tables E-1 and E-2 specified in the corresponding version of the present document, that the revision statement date of the YANG model is no earlier than the revision date as listed in the corresponding Tables E-1 and E-2 while ensuring backwards compatibility. If an O-RU indicates it supports a particular supported-mplane-version and one or more modules in its YANG library have a revision statement later than the date listed in the corresponding Tables E-1 and E-2, then an O-RU controller that supports the later module revision can exercise the functionality introduced in the later revision. O-RU Controllers that receive YANG library information from the O-RU with a module revision that is a higher version than the module revision currently used by the O-RU Controller can assume that models with the same namespace have been updated to ensure backwards compatibility. The O-RU Controller can continue to use its current module version and any unknown schema nodes and/or unknown notifications received from the O-RU, i.e. those introduced in later revisions, should be ignored by the O-RU Controller. NOTE 1: This allows an O-RU to be incrementally enhanced with functionality introduced in newer versions of the O-RAN.WG4.MP.0 specification while ensuring backwards compatible operation with O-RU Controllers compliant with the present document. NOTE 2: There have been non-backwards compatibility changes made during the development of earlier versions of the present document. This means that the YANG backwards compatibility rules described above do not accommodate these specific changes. In particular: "ORAN-WG4.MP.0-v05.00": Switched the mandatory cipher 3DES-CBC to AES128-CTR. "ORAN-WG4.MP.0-v06.00": Switched from all O-RUs required to support IPv4 to enable IPv6 only O-RUs. "ORAN-WG4.MP.0-v12.00": Switched IEEE 802.1X supplicant functionality support in O-RU from recommended to mandatory. "ORAN-WG4.MP.0-v16.01": Added Simple Public Key-based SSH Client authentication by SSH server as an option for default user authentication. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 22 "ORAN-WG4.MP.0-v17.00": Switched from importing ietf-crypto-types revision date 2022-12-12 to importing ietf-crypto-types revision date 2024-10-10. YANG features have been renamed in this switch, including: i) feature "p10-based-csrs" in revision date 2022-12-12 is renamed "p10-csr- format" in revision data 2024-10-10, and ii) feature "hidden-keys" in revision date 2022-12-12 is renamed "hidden-private-keys" in revision data 2024-10-10. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 4.4 Namespace compatibility handling | If backwards incompatible changes have been made, the <model-number> used in the YANG model namespace shall be incremented. Following such changes, an O-RU may include multiple backwards incompatible model names and namespaces in its YANG library, for example "urn:o-ran:"<model-name>":1.0" and "urn:o-ran:"<model-name>":2.0". The O-RAN Alliance's IPR policy defines terms regarding the modification of O-RAN defined specifications. When such modifications are necessary, the preferred approach for realizing such is for the third-party licensee to publish their own augmentations to the O-RAN defined YANG models and procedures. An O-RU that supports such third-party modifications shall include such model augmentations in its YANG library. Consequently, an O-RU Controller should be prepared to ignore any unknown models, e.g. developed according to such a procedure, as well as ignoring any unknown notifications defined in such models and received by an O-RU Controller that has subscribed to the O-RU's default event stream, as described in clause 9.1.7.2. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5 High level description | 5.1 Top level functional description, terminology, including hybrid, hierarchical |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.1.1 Architecture for O-RAN WG4 fronthaul functional split | This O-RAN FH specification addresses the lower layer functional split as depicted in Figure 5.1.1-1. Refer to the O-RAN CUS plane specification [2], clause 4.1 for more details on the split architecture. The Lower-Layer Split M-plane (LLS-M) facilitates the initialization, configuration and management of the O-RU to support the stated functional split. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 23 Figure 5.1.1-1: O-RAN WG4 FH functional split |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.1.2 M-Plane architecture model | A NETCONF/YANG based M-Plane is used for supporting the management features including "start up" installation, software management, configuration management, performance management, fault management and file management towards the O-RU. The M-Plane supports two architectural models: 1) Hierarchical model. As shown on the left side Figure 5.1.2-1, the O-RU is managed entirely by one or more O-DU(s) using a NETCONF based M-Plane interface. 2) Hybrid model. As shown on the right side of Figure 5.1.2-1, the hybrid architecture enables one or more direct logical interface(s) between management system(s) and O-RU in addition to a logical interface between O-DU and the O-RU. In the hybrid model, the accounts of the NETCONF clients connecting to the O-RU shall be configured with one or more privilege groups that reflect the NETCONF client's responsibilities, allowing functions like O-RU software management, performance management, configuration management, carrier configuration and fault management to be managed directly by the management system(s). NOTE 1: This avoids the situation where a NETCONF client is configured with a privilege group that does not reflect its responsibilities, and where a non-compliant client can configure aspects of an O-RU which are intended to be configured by systems associated with other NETCONF clients. A Multi-Operator O-RU shall additionally support M-Plane architecture models which involve one or more O-DUs operated by one or more different Shared Resource Operators. Clause 19.2 describes the high level shared O-RU architecture, including hybrid and hierarchical architecture models for Multi-Operator O-RU operation with one or more different Shared Resource Operators. O-DUs managing an O-RU using the hierarchical model are termed "hierarchical O-DUs" and O-DUs managing an O-RU using the hybrid model are termed "hybrid O-DUs". An O-DU may be designed to operate only as a hierarchical O-DU, only as a hybrid O-DU or as both a hierarchical and hybrid O-DU, i.e. when operating with different O-RUs. NOTE 2: How an O-DU that is designed to manage an O-RU (either as a hierarchical or hybrid O-DU) is configured to operate in a specific mode with a particular O-RU is outside the scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 24 In the hybrid model, the O-RU has end to end IP layer connectivity with the SMO. From a physical network point of view, this connectivity could be via the hybrid O-DU, where the hybrid O-DU is acting as an IP/Ethernet packet forwarder, forwards the packets between O-RU and the SMO. Direct logical communication between an O-RU and SMO can be enabled via O-RUs being assigned routable IPs or local private IPs resolved by a NAT function in the network (or implemented at the hybrid O-DU). Refer to clause 6 for details how O-RU acquires the IP address of O-DU and SMO for the M-plane communication. As described in clause 6, there is no explicit signalling to indicate that an O-RU is operating in a hierarchical or hybrid configuration. All NETCONF servers supporting this M-Plane specification shall support multiple NETCONF sessions. All O-RUs shall be able to support both hierarchical and hybrid deployment. Figure 5.1.2-1: M-Plane Architecture NETCONF/YANG is used as the network element management protocol [3] and data modelling language [4]. Use of such a standardised framework and common modelling language simplifies integration between O-DU and O-RU as well as operator network integration (in terms of running service) in case of elements sharing a common set of capabilities. The framework supports integration of products with differing capabilities enabled by well-defined published data models. NETCONF also natively supports a hybrid architecture which enables multiple clients to subscribe and receive information originating at the NETCONF server in the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.1.3 Transport network | Based on the transport topology, various modes of network connectivity are possible between O-RU and O-DU and SMO. The basic requirement for M-Plane is to have end to end IP connectivity between the O-RU and the elements managing it (O-DU, SMO, or so called "O-RU Controllers"). The connectivity between the O-DU and SMO and its management plane are not in scope of the present document. The O-RU shall support either IPv4 or IPv6 and optionally support dual stack (IPv4 and IPv6). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 25 NOTE: In previous versions of the present document, only IPv4 was mandatory. In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, an operator and vendor can agree to use a common IP version in the O-RU, O-DU and any other O-RU controllers. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 5.1.4 M-Plane functional description | The M-Plane provides the following major functionalities to the O-RU. These features are implemented using the NETCONF provided functions. "Start-up" installation During start-up, the O-RU acquires its network layer parameters either via static (pre-configured in the O-RU) or dynamically via DHCP or DHCPv6. During this process the O-RU may acquire the IP address of the O-RU controller(s), in which case the O-RU establishes the NETCONF connectivity using the "call home" feature. When the O-RU is operating in an environment which include the O-RAN defined SMO, the O-RU may acquire the IP address of the event-collector(s), in which case the O-RU performs a pnfRegistration which triggers the SMO to establish NETCONF connectivity using the information recovered from the pnfRegistration procedure. The capability exchange is performed between the client and server as part of the initial NETCONF Hello exchanges. Details of these steps are provided in clause 6. NOTE 1: The use of "start up" terminology in the present document is distinct from the "start-up" capability used in a NETCONF environment to indicate that a device supports separate running and startup configuration datastores. NOTE 2: The O-RU Controller can also be used to configure additional network layer parameters, as described in clause 6.2.1. The present document makes specific reference to configuration which is required to be stored in "reset persistent memory". The O-RU shall use this stored configuration as its "startup" configuration. SW management The M-Plane is used for software download, installation, validation and activation of new SW when requested by O-RU Controller. The software download is triggered by NETCONF RPC procedures, and the actual software download is performed using sFTP with SSH or FTPES with TLS as specified in IETF RFC 4217 [54]. Configuration management Configuration management covers various scenarios like Retrieve Resource State, Modify Resource State, Modify Parameters and Retrieve Parameters. NETCONF get-config and edit-config RPCs shall be used for configuration parameter retrieval and updates at the O-RU Performance management Performance management describes the measurements and counters used to collect data related to O-RU operations. The purpose of Performance Management is optimizing the operation of the O-RU. The measurement results are reported by two options: 1) YANG Notification: This option uses the stats definition of YANG model per measurement group. In this case, get RPC and/or notification are used (see clause 10 for more details). 2) File Upload: This option uses the file upload procedure defined in clause12. The measurement results are saved to a data file periodically. Fault Management Fault management is used for sending alarm notifications to the NETCONF Client. Fault Management allows alarm notifications to be disabled or enabled as well as alarm subscription. File Management File management allows the O-RU Controller to trigger an O-RU to perform upload of files stored on O-RU to O-RU Controller. The O-RU may provide different kinds of files and retrieved files can be used for various purposes. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 26 Simultaneous multiple file upload operations can be supported under the same sFTP or FTPES connection between O-RU to O-DU/SMO. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.