hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.5.2 Data Plane: DVB-MABR | DVB-MABR has been specified to be independent from the underlying transport protocol. ETSI TS 103 769 [8] specifies two multicast media transport protocols in its annexes. • The FLUTE protocol specified in Annexes F and G of ETSI TS 103 769 [8] is based on 3GPP MBMS FLUTE and may be used for the carriage of NIP Streams... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8 Service Signalling Protocols | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1 Signalling Overview | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.1 Introduction | DVB-NIP Signalling, as defined in the present document, relies on the concept of a broadcast Announcement Channel carrying signalling information under the form of XML Tables to NIP receivers. The Announcement Channel mechanism is defined under clause 8.2. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.2 Signalling Data Structures | DVB-NIP signalling information is split across 6 tables. The purpose of these tables is to inform NIP receivers about: 1) The technical parameters required to access DVB-NIP services. 2) The availability of Service Lists, Services and content on the broadcast network and potentially via broadband. The first table is ca... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.3 Service Delivery Model | A DVB-NIP broadcast network is made up of one or more RF Channels (called transponders in a satellite context). Each RF Channel can carry one or multiple Input Stream Identifiers (ISIs) as defined in DVB-S2X (ETSI EN 302 307-1 [1], ETSI EN 302 307-2 [2]) or one or more Physical Layer Pipes (PLPs) as defined in DVB-T2 (... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.4 Bootstrap and Regular NIP Streams | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.4.1 Definition | DVB-NIP distinguishes two types of streams: so-called Bootstrap NIP Streams and Regular NIP Streams. Bootstrap Streams participate in the bootstrap setup phase of receivers and shall carry NIF, SIF and DVB-I Service List Entry Points. If one or more of these documents are missing, the Stream cannot be considered as Boo... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.4.2 NIP Stream Identifiers | NIP Streams are identified by the following 4 parameters: • NIPNetworkID identifying the network. • NIPCarrierID identifying uniquely the RF Carrier within the network identified with NIPNetworkID. • NIPLinkID identifying the NIP Stream in the context of DVB-GSE (ETSI TS 102 606-2 [5]) or in the context of DVB-S2 Profe... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.5 Table Generation and Broadcast | DVB-NIP tables are generated as files by the NIP Service Aggregation Platform and broadcast from the NIP Headend. The Signalling Server function of a NIP Headend collects or generates the signalling information and converts it for multicast transmission via the broadcast Announcement Channel. Every NIP Stream shall car... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.6 Signalling Broadcast Location | DVB-NIP tables are carried via the Announcement Channel mechanism described under clause 8.2. The Announcement Channel shall be present in every NIP Stream. Figure 8.1.6-1: Signalling carriage in NIP Streams Mandatory on the shown NIP stream Optional on the shown NIP stream Not required for MPE Streams MPD Bootstrap mc... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7 Receiver Signalling Usage Sequence | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.1 Introduction | The clauses hereunder describe the different steps that a NIP receiver follows in order to gain access to NIP services. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.2 Receiver Bootstrapping Mechanism | A NIP receiver, in idle mode, joining a NIP broadcast network initially tunes to the Bootstrap Stream and listens for the NIF, SIF tables and DVB-I Service List Service Entry Points document on the announcement channel of that stream. A NIP Bootstrap Stream is identified thanks to: • The NIP Stream identifiers as defin... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.3 Device Announcement and Discovery Mechanism | NIP receivers according to Deployment Model 3 (DM3) implement a functional split between the DVB-I Client rendering the services to end users and the NIP Gateway which receives the content from the broadcast network. NIP specifies two main mechanisms in clause 11.1 which allow both NIP Clients and NIP Gateways to annou... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.4 DVB-I Service List Discovery Mechanism | DVB-I Clients contact the local DVB-I Service List Registry (SLR) function part of the NIP Gateway to get the DVB Service List Entry Points table. That table lists all the DVB-I Service Lists available on the broadcast network. A DVB-I Client shall request from the NIP Gateway: 1) the entire list that the Gateway recei... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.5 DVB-I Service Discovery Mechanism | Once the DVB-I Client has received the entire or down-filtered list of DVB-I Service Lists available on the broadcast network it can itself or through interaction with the end-user select the DVB-I Service List to use for the selection of DVB-I Services. The DVB-I Client will request the selected DVB-I Service List fro... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.1.7.6 Service Tuning and Service Access Mechanism | Each time the end-user selects a broadcast service instance from the DVB-I Service List, the DVB-I Client function sends a request for the MPEG-DASH manifest to the NIP Gateway function. These instance requests are automatically sent to the Gateway due to the format of the URLs for such instances. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2 Signalling Carriage Description | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.1 Principles | Every NIP GSE-Lite/MPE stream according to the present document shall carry an announcement channel on a fixed IP multicast address, UDP port number. The announcement channel shall use the FLUTE or ROUTE protocol specified in Annexes F and G of DVB-MABR ETSI TS 103 769 [8] to carry the signalling information required f... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.2 IP Multicast Address, Port and TSI | Signalling information shall be carried as document files in a FLUTE/ROUTE session with a well-known IP address, UDP port number and TSI (LCT) dedicated to this function. The IP address has been registered by DVB (dvbservdsc) with IANA described in IETF RFC 5328 [19] and is 224.0.23.14 for IPv4 and FF0X:0:0:0:0:0:0:12D... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.3 Announcement Channel Structure | The Announcement Channel stream consists of a FLUTE/ROUTE session with TSI 0 using the IP multicast address and UDP port specified in clause 8.2.2. NIP Bootstrap Stream Multicast session Service X Multicast transport session (FLUTE/ROUTE Session) A176r3 clauses 8.3.4, 10.2.3 Service X vision component Carousel Presenta... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.4 Announcement Channel FLUTE/ROUTE File Delivery Table | The announcement channel FLUTE/ROUTE session carries the mandatory File Delivery Table (FDT) as specified in DVB-MABR ETSI TS 103 769 [8]. The FDT is used to inform receivers about the files that are being transmitted and their associated metadata. FDT instances are sent in the same session as the files. The FDT itself... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.5 Announcement Channel Content | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.5.1 Signalling Data | The announcement channel carries the actual signalling documents required by NIP. Signalling information is carried as different XML formatted documents among which the following: • Bootstrap multicast gateway configuration instance document. • NIP Network Information File. • NIP Service Information File. • DVB-I Broad... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.5.2 Payload Data Updates | The semantics for any two "File" elements declaring the same "Content-Location" but differing "TOI" is that the element appearing in the FDT Instance with the greater FDT Instance ID is considered to declare a newer instance (e.g. version) of the same "File". |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.5.3 Payload Data Compression | As the signalling payload information consists of XML files which are verbose, payload data compression may be applied. If compression is applied it shall be signalled as part of the FDT. The attribute "Content-Encoding" shall be used as defined in DVB-MABR ETSI TS 103 769 [8]. When present its value indicates what dec... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.6 Announcement Channel Repetition Rates | Table 8.2.6-1 lists the minimum repetition times for each table carried via the NIP announcement channel. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 45 Table 8.2.6-1: Minimum table repetition rates Description Table Repetition Rate (at least once every x seconds) Bootstrap multicast gateway configuration instance document 1... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.7 URL Coding in NIP documents | URLs coded in NIP documents shall use the following syntax: wherein the absolute path is used to store and locate documents at the level of the NIP Gateway. NOTE: The domain name "dvb.gw" cannot be publicly resolved and is only meant to be used in the context of DVB-NIP table broadcasts. It is recommended for the first... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.2.8 NIP Announcement Channel Document Storage Location | Each time the NIP Gateway tunes to the NIP Bootstrap Stream, all documents carried by the NIP Announcement Channel shall be cached or updated in the root folder of the NIP Gateway. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 46 |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3 Service Discovery and Programme Metadata: DVB-I | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.1 Overview | DVB-NIP relies on DVB-I for Service Discovery and Program Metadata as specified in ETSI TS 103 770 [9]. A DVB-NIP broadcast network according to the present document shall carry at least one DVB-I Service List listing the services available on the broadcast network. Larger broadcast networks may carry several DVB-I Ser... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.2 DVB-I Broadcast List Discovery: Service List Entry Points | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.2.1 Principles | For DVB-NIP Receivers to discover all the DVB-I Service Lists available on the broadcast network, the DVB-I Service List Entry Points mechanism as specified in clause 5.3 of DVB-I ETSI TS 103 770 [9] shall be used. The DVB-I Service List Entry Points mechanism is used to provide a table to NIP Receivers listing all DVB... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.2.2 DVB-I Broadcast Service List Discovery: Service List Registry Function | The Broadcast DVB-I Service List Entry Points file is multicast as a pre-compiled file (listing all the DVB-I broadcast Service Lists on the actual network) within the DVB-NIP Announcement Channel on the bootstrap stream. It is used by the Service List Registry (SLR) function part of the NIP Gateway. The Service List R... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.3 DVB-I Broadcast Service Lists | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.3.1 Introduction | Services made available via DVB-NIP compliant broadcast networks shall be signalled using the DVB-I Service List mechanism specified in clause 5.5 of ETSI TS 103 770 [9]. All syntactical elements specified in ETSI TS 103 770 [9] are also available in NIP. In a DVB-NIP compliant broadcast network, DVB-I service lists ar... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.3.2 NIP Service Instances in DVB-I Service Lists | NIP Broadcast Services shall be declared in DVB-I Service Lists as Service instances according to 5.5.4 of ETSI TS 103 770 [9]. NIP Service declarations shall use the DVB-I declared "DASHDeliveryParametersType" as defined in clause 5.5.18.6 of ETSI TS 103 770 [9]. The URL within the "URIbasedLocation" shall point towar... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.3.4 DVB-I Related Materials | DVB-I Related Materials refers to: • Logos associated to the DVB-I Broadcast Service Lists themselves as listed in the DVB-I Service Lists Entry Points document. • Logos of the services listed in DVB-I Service Lists. Logos associated to DVB-I PlaylistsDVB-I Related Materials may be carried in one or more dedicated mult... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4 Broadcast Network Signalling: NIF and SIF | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.1 Overview | The main purpose of Broadcast Network Signalling is to describe the broadcast network with its logical streams and their physical channel parameters and the location of services across those streams. DVB-NIP defines two tables that describe the broadcast network: • NIF: The Network Information File provides logical and... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2 Network Information File (NIF) Definition | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.1 NIF Purpose | The Network Information File (NIF) describes the broadcast network. It provides information about the logical streams and physical parameters of the different RF Channels in a particular broadcast network. In that sense it is comparable to the function of the NIT in traditional DVB systems. ETSI ETSI TS 103 876 V1.1.1 ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2 Network Information File | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.1 NIF Schema Declaration | <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="urn:dvb:metadata:nativeip:2023" xmlns:mpeg7="urn:tva:mpeg7:2008" targetNamespace="urn:dvb:metadata:nativeip:2023" elementFormDefault="qualified"> <xs:import namespace="urn:tva:mpeg7:2008" schemaLocation="tva_mpeg7.xs... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.2 NetworkInformationFileType | <xs:complexType name="NetworkInformationFileType"> <xs:sequence> <xs:element name="VersionUpdate" type="xs:dateTime"/> <xs:element name="NIFType"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Physical Network"/> <xs:enumeration value="Commercial Operator"/> </xs:restriction> </xs:simpleType>... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.3 BroadcastNetworkType | <xs:complexType name="BroadcastNetworkType"> <xs:sequence> <xs:element name="NetworkType"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="Satellite"/> <xs:enumeration value="Terrestrial"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="NetworkName" type="xs:string"/> <xs:el... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.4 SatellitePositionType | <xs:complexType name="SatellitePositionType"> <xs:sequence> <xs:element name="OrbitalPosition"> <xs:simpleType> <xs:restriction base="xs:double"> <minInclusive value="0.0"/> <maxInclusive value="180.0"/> </xs:restriction> </xs:simpleType> <:xs:element> <xs:element name="West_East_flag"> <xs:simpleType> <xs:restriction ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.5 NIPStreamType | <xs:complexType name="NIPStreamType"> <xs:sequence> <xs:element name="LinkLayerFormat"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="GSE-Lite"/> <xs:enumeration value="TS"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="NIPStreamProviderName" type="sd:ProviderName"/> <xs... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.6 DeliveryParametersTypes | 8.4.2.2.6.1 DVBS2_NIPDeliveryParametersType <xs:complexType name="DVBS2_NIPDeliveryParametersType"> <xs:sequence> <xs:element name="Frequency" type="xs:positiveInteger"/> <xs:element name="Polarization" type="string"/> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="horizontal"/> <xs:enumeratio... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.2.2.7 NIF Example | The following NIF.xml example depicts a Satellite Technical Operator declaring: • 2 NIP Streams belonging to the same NIPNetworkID. One of them is declared as Bootstrap Stream. • 1 NIP Stream, on the same orbital position but with different NIPNewtorkID. • 1 NIP Streams, declared as a Bootstrap, from another orbital po... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3 Service Information File (SIF) Definition | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.1 SIF Purpose | The Service Information File (SIF) describes, for each stream identified logically, the location of: • DVB-I Service Lists; • Service manifests; • DVB-I Playlists; • DVB-I Content Guide Sources; • Interactive Applications not linked directly to a particular service. The SIF is one of the three mandatory tables to be br... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.2 Service Information File | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.2.1 SIF Schema Declaration | <?xml version="1.0" encoding="UTF-8"?> xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="urn:dvb:metadata:nativeip:2023" xmlns:mpeg7="urn:tva:mpeg7:2008" targetNamespace="urn:dvb:metadata:nativeip:2023" elementFormDefault="qualified"> <xs:import namespace="urn:tva:mpeg7:2008" schemaLocation="tva_mpeg7.xsd... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.2.2 ServiceInformationFileType | <xs:complexType name="ServiceInformationFileType"> <xs:sequence> <xs:element name="VersionUpdate" type="xs:dateTime"/> <xs:element name="NIPNetworkProviderName" type="sd:ProviderName" /> <xs:element name="BroadcastMediaStream" type="ns:BroadcastMediaStreamType" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> </xs:... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.2.3 BroadcastMediaStreamType | <xs:complexType name="BroadcastMediaStreamType"> <xs:sequence> <xs:element name="NIPNetworkID"> <xs:simpleType> <xs:restriction base="xs:unsignedShort"> <xs:minInclusive value="1"/> <xs:maxInclusive value="65280"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="NIPCarrierID"> <xs:simpleType> <xs:res... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.2.4 Interactive Applications signalling structure | Interactive applications signalled in a SIF are specific to operators, identified with their ProviderName, e.g.: HbbTV OpApp. Such signalling cannot be used to declare interactive applications linked to a NIP Service, as such mechanism is specified by DVB-I (ETSI TS 103 770 [9]). ETSI ETSI TS 103 876 V1.1.1 (2024-09) 6... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.4.3.4.5 SIF Example | The following SIF.xml example depicts a Satellite Technical Operator declaring: • 9 broadcast streamed services over 3 NIP streams, from 3 different Providers • 3 DVB-I Service Lists over 2 NIP Streams • 1 DVB-I Content Guide Source • 1 HbbTV OpApp <?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="UT... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.5 DVB-MABR Adaptation and Signalling | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.5.1 Introduction | The present document relies on the DVB Multicast ABR specification (ETSI TS 103 769 [8]) for transporting ABR-coded Media Objects via multicast streaming over the DVB-NIP Broadcast System. Figure 8.5.1-1, extracted from ETSI TS 103 769 [8] represents the DVB MABR simplified architecture. This clause describes a unidire... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.5.2 Multicast Gateway Configuration | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.5.2.1 General | The Multicast Gateway is configured through at least one of the four methods defined in clause 10.1.2 of ETSI TS 103 769 [8]. In unidirectional NIP deployments, the Multicast Gateway configuration shall be provided through either the in-band method or the just-in-time method. The multicast gateway configuration instanc... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.5.3 DVB-MABR Operation and Workflow | The NIP Gateway shall instantiate a Multicast Gateway and Multicast Rendezvous Service as specified in clause 7.2 of ETSI TS 103 769 [8] and these instantiations shall be compliant with the following specification. The NIP Gateway shall follow the mode of operation specified in clause 7.2 of ETSI TS 103 769 [8]. The fo... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6 Time Synchronization | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.1 NIP Wall Clock | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.1.1 EXT_TIME Header Extension | The Multicast Server shall broadcast its current time using the Network Time Protocol (NTP) format as specified in IETF RFC 1305 [25]. The NTP time shall be delivered in the EXT_TIME LCT extension header of LCT packets as defined in section 5.2.2 of IETF RFC 5651 [26]. EXT_TIME shall provide Sender Current Time (SCT) w... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.1.2 Carriage of Timing Information | EXT_TIME shall be included in each LCT packet with TOI=0. These packets are used to carry the File Delivery Table (FDT). To be clear all FLUTE/ROUTE transport sessions in NIP shall convey the NTP UTC reference time, not only FLUTE/ROUTE sessions carrying NIP Announcement Channel data. Receivers shall use the NTP inform... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.1.3 Global Time Reference | NTP time as carried by the NIP Announcement Channel FLUTE/ROUTE carousel of the bootstrap stream shall be used as the global time reference. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 73 |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.2 Local Time Offset | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.2.1 Time Offset File | The Time Offset File (TOF) is used to convey all possible time offset values and date saving flags and related parameters. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.2.2 TOF Schema Declaration | <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="urn:dvb:metadata:nativeip:2023" xmlns:mpeg7="urn:tva:mpeg7:2008" targetNamespace="urn:dvb:metadata:nativeip:2023" elementFormDefault="qualified"> <import namespace="urn:tva:mpeg7:2008" schemaLocation="tva_mpeg7.xsd"/... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.2.3 TimeOffsetFileType | <xs:complexType name="TimeOffsetFileType"> <xs:sequence> <xs:element name="VersionUpdate" type="xs:dateTime"/> <xs:element name="country_code"> <xs:simpleType> <xs:restriction base= "xs:string"> <xs:pattern value="[A-Z][A-Z][A-Z]"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="country_region_Id" m... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.2.4 TOF Example | <?xml version="1.0" encoding="UTF-8"?> <TimeOffsetFile xmlns="urn:dvb:metadata:nativeip:2022" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xsi:schemaLocation="urn:dvb:metadata:nativeip:2022 ../TimeOffsetFile.xsd"> <VersionUpdate>2021-12-20T23:00:00Z</VersionUpdate> <country_code>FRA</country_code> <local_time... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.6.3 Time Synchronization between DVB-I Client and NIP Gateway | The NIP Gateway shall expose the NIP Wall Clock via http://dvb.gw/time. The default time format shall be xs:dateTime as defined in W3C XML Schema Part 2 [i.3]. The following additional queries shall be supported: • iso: time value formatted according to ISO time code as defined in ISO/IEC 8601-1 [23]. • xsdate: time va... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.7 IP Layer Identification of RF Carriers | 8.7.1 Object In order for a NIP Gateway to ascertain the reception of a given RF Transport Carrier (e.g. a particular satellite transponder), information about the actually tuned to RF Carrier has to be available to NIP Receivers. For this reason, network operators shall insert the following information into all NIP St... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 8.7.3 NIP Actual Carrier Information Format | NIP Actual Carrier Information shall be provided in the EXT_NACI extension header of LCT packets. The EXT_NACI is a Protocol Instantiation specific (PI-specific) LCT extension defined with Header Extension Type (HET) = 68. The ALC/LCT packet carrying the NIP Actual Carrier Information extension (EXT_NACI) shall not hav... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9 Application and Presentation Layer | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.1 Audio and Video Coding Standards | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.1.1 Overview | DVB-NIP only requires a single mandatory system format for the carriage of audio-visual presentations: MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks ETSI TS 103 285 [11]. Audio Video Coding and Packaging for Native IP Adaptive Bit Rate applications shall be according to ETSI TS 1... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.1.2 MPEG-DASH AV Synchronization in NIP | While using the NIP defined FLUTE/ROUTE file transfer protocols, the NIP Multicast Server leaves timing information in MPEG-DASH manifest files unchanged from the origin. The MPEG-DASH manifest files broadcast via NIP therefore may or may not contain any time related information. The Multicast Gateway shall ensure that... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.2 Captions and Subtitles | NIP Clients shall be able to correctly render TTML based subtitles according to clause 7 of DVB-DASH (ETSI TS 103 285 [11]). |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.3 Time Shifting | Timeshifting for connected receivers shall be according to ETSI TS 103 285 [11]. Timeshifting for unconnected receivers is outside the scope of the present document. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.4 Service Usage Reporting | Service Usage Reporting for connected receivers shall be according to clauses 5.3.6.1, 5.3.8.4, 10.2.2.3 and 11 of ETSI TS 103 769 [8]. Service Usage Reporting for unconnected receivers is outside the scope of the present document. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5 Generic File Delivery | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.1 Introduction | In addition to delivering audio-visual content for live consumption and related signalling, DVB-NIP also provides mechanisms for pushing any type of generic offline file-based content to NIP Receivers. These mechanisms apply to the following applications in NIP: • NIP Broadcast Content and Service Guide as specified in... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.2 NIP Object Carousels in DVB-MABR Multicast Transport Sessions | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.2.1 Identifying a NIP MulticastGatewayConfiguration Transport Session | NIP generic file-based data shall be carried in object carousels inside DVB-MABR Multicast Transport Sessions (as defined in ETSI TS 103 769 [8]) and shall be identified in the bootstrap multicast gateway configuration instance document using the following two identifiers (attributes) introduced in clause 10 of ETSI TS... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.2.2 Multicast Transport Session Tagging | The example document below shows a declaration of a multicast gateway configuration transport session as used in NIP with the tagging mechanism defined in clause 9.5.2.1. Such tags shall allow to uniquely refer to a session from other NIP documents. <?xml version="1.0" encoding="UTF-8"?> <MulticastGatewayConfiguration ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.3 NIP Application-specific Manifest Files | Depending on the actual NIP application, additional information not currently available through DVB-MABR will be provided to NIP Gateways through so-called NIP Application Manifest files. These Manifest files are NIP application- specific and can be compared to the Manifest files which are provided with e.g. DVB-DASH s... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.4 URI-based Re-Tuning of Broadcast Receivers | The DVB-NIP system inherently relies on a URI-based re-tuning mechanism for NIP Gateways. NIP Gateways are aware of where URI objects are carried on the broadcast network thanks to the SIF described in clause 8.4.3. The purpose of the SIF is to associate URIs to BroadcastMediaStreams. This allows NIP Gateways to automa... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.5 NIP Gateway Workflow | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.5.1 From Application Manifest to Content Download | This clause describes the generic workflow of a NIP Gateway in the context of Applications making use of the Generic File Delivery mechanism. As a prerequisite to such operation, it is assumed that the NIP Gateway has been installed and has downloaded all the information carried in the Announcement Channel of its Boost... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.5.2 NIP Gateway File Content Repository | The Application-specific content downloaded from the broadcast network shall be stored within the NIP Gateway file structure according to the path specified in the <ResourceLocator> element of the Bootstrap Multicast Gateway Configuration Instance document or alternatively the matching Content-Location field in the FDT... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 9.5.6 DVB-MABR Multicast Server Generic File Ingest Interface: NH2 | NH2 represents the interface between the Multicast Server and the content hosting origin for Generic File based data. The Ingest function determines the data to be broadcast as part of NIP Object Carousels. If available, the Generic File Ingest function may use the Multicast Server Configuration generated by the DVB-MA... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10 Content Protection | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.1 Introduction | Content protection signalling shall be according to clause 8.4 of DVB-DASH ETSI TS 103 285 [11]. DVB NIP does not specify a full end-to-end content protection system (DRM). Multicast Server FLUTE/ROUTE Multicast transmission Fixed IP multicast NIP Service Aggregation Platform DVB-I Broadcast Service List(s) Cloud or On... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.2 Connected Receivers | In the case of DVB-I Clients connected to a NIP Gateway and/or to an IP network via broadband, the DVB-I Client secure player shall comply to content protection mechanisms as specified in DVB-DASH ETSI TS 103 285 [11]. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3 Unconnected Receivers (informative) | 10.3.1 Broadcast Delivery of Content Protection Assets to Secured DASH Players |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.1 Introduction | Any proprietary DRM solution can be integrated in a DVB-NIP workflow to provide credentials to secured DASH players. This feature is optional, but if implemented, it shall comply with the specification as given in the following sections. DVB-NIP specifies the way to signal and convey the required security assets to NIP... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.