hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4.4 PSAP operator user interface | Interoperability Test Description Identifier: TD_ADV_PSAP_04 Objective: Verify that the PSAP user interface displays caller identity, caller location and MSD. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 References: Clause 6.2.4 of EN 16072:2022 [7] Applicability: IVS_ims_eCall AND PSAP_ims_eCall Pre-test conditio... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.4.5 Invalid MSD | Interoperability Test Description Identifier: TD_ADV_PSAP_05 Objective: Verify that the PSAP performs a format and consistency check of an invalid (or corrupted) initial MSD and hereafter provides a 200 OK INVITE response with a negative acknowledgement for the MSD. Configuration: NG_eCall_CFG_01 or NG_eCall_CFG_07 Ref... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.5 Advanced Tests for TPS | |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.5.1 TPSP and rerouting to national PSAP | Interoperability Test Description Identifier: TD_ADV_TPS_01 Objective: Verify that TPSP is able to reroute the eCall to the national PSAP/emergency control centre, in order to transfer the MSD and establish a voice connection with the national PSAP. Configuration: NG_eCall_CFG_09 References: Clauses 9.9, 10.3 and 10.4 ... |
abc7314f616c8b693b9b3d112999b441 | 103 683 | 7.5.2 Conference call between TPS IVS, TPSP and national PSAP | Interoperability Test Description Identifier: TD_ADV_TPS_02 Objective: Verify that TPSP is able to forward the eCall to the national PSAP/emergency control centre, in order to transfer the MSD and establish a conference call between TPS IVS, TPSP and national PSAP. Configuration: NG_eCall_CFG_09 References: Clauses 9.3... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 1 Scope | The present document defines the following: • signalling of linear TV or radio services and content that are delivered over broadband; • access linear TV services that are delivered by broadband in a way that is consistent with their access to linear TV services delivered by RF-based DVB technologies; • the metadata an... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 2 References | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 3 Definition of terms, symbols and abbreviations | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 285 [1] and the following apply: DVB-I client: implementation of the client side of the present document NOTE: This may be integrated into the User Interface (UI) of a device such as a television or set-top box or part of an app on devices such as... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 3.2 Symbols | Void. ETSI ETSI TS 103 770 V1.1.1 (2020-11) 14 |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form ABR Adaptive Bit Rate AES Advanced Encryption Standard AIT Application Information Table API Application Programming Interface ASCII American Standard Code for Information Interchange AVC Advanced Video Coding B... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 4 Architecture | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 4.1 DVB-I components and interfaces | Figure 1 below shows a simplified view of DVB-I components and the interfaces between them. Some missing elements include: i) CDNs; ii) service list server discovery; iii) encoding of the video and audio streams; ETSI ETSI TS 103 770 V1.1.1 (2020-11) 16 iv) distributing video and audio streams from the content/service ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 4.2 Conceptual model of a DVB-I client | Figure 2 illustrates a conceptual model of a hypothetical DVB-I client. Figure 2: Conceptual model of a DVB-I client Here is more detail on the components. • Source selection UI: Devices hosting a DVB-I client will typically have some kind of UI allowing the user to choose between one or more inputs, sources or apps. A... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5 Service Discovery | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1 Concepts | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.1 Services | A DVB-I service is one which is discovered using the present document and which is available via one or more delivery mechanisms, called service instances, including DVB-DASH and traditional DVB broadcast. Such a DVB-I service: • may be delivered over an IP network, either with or without ABR multicast, etc., or it may... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.2 Service Lists | The DVB-I client accesses information about services through Service Lists. Service Lists are published by Service List Providers. A Service List typically lists services from many content providers. The role of the Service List Provider is to curate and manage the Service List and provide service ordering and numberin... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.3 Service List Discovery | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.3.1 Client options for service list discovery | A DVB-I client requires a means to find one or more Service Lists. This is referred to as Service List Discovery. DVB-I supports two principal approaches to Service List Discovery: • The client may have one or more built-in or privately provisioned Service List URLs for the specific Service List(s) that the client wish... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.3.2 Service List Registry | A DVB-I Service List Registry (SLR) is an HTTP endpoint available at a known URL that, if queried, can return a list of Service List Entry Points. A DVB-I Service List Provider who wishes to enable the SLR discovery mechanism for their own Service Lists may register their Service List Entry Points in the SLR using the ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.3.3 Announcement of a DVB-I Service List in a broadcast channel | Broadcasters may signal the URL of a DVB-I service list or a query to a Service List Registry in the DVB-SI metadata. To this purpose, a URI linkage descriptor in the 1st loop of NIT or the 1st loop of BAT shall be used in accordance with the scoping rules defined in clause 6.5 of ETSI EN 300 468 [6], with uri_linkage_... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.4 Relationships | Figure 3 summarizes the concepts of Service List Registry, Service List and Service. Figure 3: Relationships among Service List Entry Point, Service List, Service and LCN Table A single Service can be listed in many different Service Lists and may have a different channel number in each. A Service List can include many... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.5 Subscription Packages | The optional element SubscriptionPackage contains a human readable label for a service provider defined subscription package, that applies to an LCN Table (see clause 5.5.12) or a service instance (see clause 5.5.4), and corresponds to the name of a package that a user can subscribe to. It can be used at different leve... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.1.6 Linked applications | Services in a service list may have applications linked to them according to signalling defined in clause 5.2.3. Such linked applications may be used for a number of purposes including but not limited to the following: • Adding value to linear television content in a similar way as "red button" applications add value t... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2 Procedures | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.1 Service Instance Matching | A hybrid DVB-I client may have one or more tuners for receiving DVB-T/C/S services, in addition to DVB-DASH services discovered using the present document. Such a hybrid DVB-I client may receive instances of the same DVB service via different DVB broadcast delivery systems. Each DVB service instance may differ in quali... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.2 Service Identifiers | Service identifiers shall use a registered URI scheme that allows independent allocation and ensures global uniqueness. Suitable URI schemes include the "tag" URI scheme as defined in IETF RFC 4151 [3]. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3 Signalling of Applications in the Service List | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3.1 General | A RelatedMaterial element can be used to signal the location of an application associated with the service or service instance. The RelatedMaterial element shall contain the following two subelements: • A HowRelated element with an @href attribute carrying a value from the urn:dvb:metadata:cs:LinkedApplicationCS:2019 c... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3.2 Applications and Media Presentation | Application with media in parallel Where an application (with any MediaURI@contentType) is signalled using a RelatedMaterial element with a HowRelated@href attribute set to urn:dvb:metadata:cs:LinkedApplicationCS:2019:1.1, the RelatedMaterial element provides initial application signalling for use when the service is a... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3.3 Dynamic Application Signalling in Services | DVB-I metadata provides quasi-static application signalling. Certain service instance types can also carry dynamic application signalling. This clause describes those and their relationship with signalling carried in DVB-I metadata. The DVB-I client that supports service instances delivered using MPEG-2 Transport Strea... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3.4 Application Signalling Precedence | Applications can be referenced at service or service instance level. A RelatedMaterial element within a ServiceInstance element referencing an application with a HowRelated@href attribute set to urn:dvb:metadata:cs:LinkedApplicationCS:2019:1.1 or urn:dvb:metadata:cs:LinkedApplicationCS:2019:1.2 overrides any RelatedMat... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.3.5 Example | An example of an XML AIT for a linked application is shown in figure 4. <?xml version="1.0" encoding="UTF-8"?> <mhp:ServiceDiscovery xmlns:mhp="urn:dvb:mhp:2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <mhp:ApplicationDiscovery DomainName="channel7.com"> <mhp:ApplicationList> <mhp:Application> <mhp:appNa... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4 Signalling of Applications in the Content Guide | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.1 General | Signalling within the content guide metadata provides deep links to applications which control presentation of the content (on-demand and live streams). A DVB-I client shall determine both content availability and its capability of playing the content before an item of content is indicated as available to the user. Whi... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.2 Application Priority | There may be multiple applications listed in an XML AIT. When determining which to launch the client shall process each application in turn and select the application with the highest mhp:priority value that meets all of the following criteria: • Application type equals application/vnd.hbbtv.xhtml+xml - This shall be s... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.3 On Demand deep-linked XML AIT | The purpose of the On Demand deep-linked XML AIT is to provide a mechanism to launch directly to a specific piece of content within a Content Provider's player application. Within the XML AIT the concatenation of URLBase and applicationLocation shall form a URL specifying an application launch location that allows laun... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4 Template XML AIT | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.1 Introduction | The purpose of the template XML AIT is to allow a client device to determine if it has a compatible environment to play the associated content, allowing a generic way to determine support for all content from which it is referenced, and thus requiring the download and processing of just one XML AIT for all the referenc... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.2 On Demand Programmes | Within every OnDemandProgram element supplied through the content guide interface there shall be an AuxiliaryURL referencing a Template XML AIT. This XML AIT is identical to the content deep-linked XML AIT (provided via the ProgramURL element) except that the content specific identifiers have been removed. The mhp:appl... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.3 Restart | Alongside every Restart XML AIT supplied through the content guide interface there shall be a Template XML AIT. This is found in RelatedMaterial element with a HowRelated element with an @href attribute carrying the value urn:fvc:metadata:cs:HowRelatedCS:2018:restart within a Schedule.ScheduleEvent.InstanceDescription ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.4 Box Sets | Every Box Set in a Box Set List response shall have an associated Template XML AIT. This represents the Template AIT (i.e. required capability) for every content item in the Box Set. This is found in the GroupInformation fragment describing the Box Set, in a RelatedMaterial element with a HowRelated element with an @hr... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.5 Template XML AIT Refreshing | The client device shall respect the Expires header and/or Cache-Control: max-age header when retrieving Template XML AIT documents, refreshing any cached Template XML AITs at the next opportunity once the timestamp/duration is reached. If no Expires or max-age header is provided the client device shall assume an expiry... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.4.4.6 Contextual Parameters | In order to allow applications to behave in a contextual and regionally aware manner, additional parameters are required to be passed in the URL when retrieving any Template XML AIT, OnDemand Deep-linked XML AIT or Service Deep-linked XML AIT. Client devices shall append all of the following parameters to the XML AIT U... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.5 Signalling of Part Time Services | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.5.1 General | Services are anticipated to operate all day, every day, however there are likely to be some exceptions to this, for example live services that may only be present during an actual event or regional services that supersede national services. A service, or a replacement for a service, can be specified as being only avail... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.5.2 Scheduled Service Hours | For service instances that are not always available, an Availability element shall be added into the service instance to denote the hours of days, days of week and weekly cadence that the service instance is available. A description of the Availability element is given in clause 5.5.15. Any number of Period elements ca... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.5.3 Service selection outside Scheduled Service Hours | If the DVB-I client selects a part time service at a time that is outside of the scheduled hours for all service instances or when all service instances of a currently selected service become unavailable, several options are possible: • The application signalled for the service (refer to clause 5.2.3) can be started. T... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.6 Logos | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.6.1 Service List Logos | Logos for the service list shall be signalled in a RelatedMaterial element within the service list with the following: • A HowRelated element with an @href attribute carrying the value urn:dvb:metadata:cs:HowRelatedCS:2020:1001.1. This classification scheme is defined in clause D.1. • Optionally a Format element contai... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.6.2 Service Logos | Logos for the service shall be signalled in a RelatedMaterial element within the service with the following: • A HowRelated element with an @href attribute carrying the value urn:dvb:metadata:cs:HowRelatedCS:2020:1001.2. This classification scheme is defined in clause D.1. • Optionally a Format element containing a Sti... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.6.3 Content Guide Source Logos | Logos for the content guide source shall be signalled in a RelatedMaterial element within the service list with the following: • A HowRelated element with an @href attribute carrying the value urn:dvb:metadata:cs:HowRelatedCS:2020:1002.1. This classification scheme is defined in clause D.1. • Optionally a Format elemen... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.7 Description of DVB-I linear services and playlists | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.7.1 General | A DASH service instance can be either a linear service, i.e. a broadcast of scheduled programmes not streamed to a specific user, or a sequence of VoD streams, i.e. a playlist. A playlist can be static, i.e. the same sequence of audio/video assets is provided to all users, or dynamic/personalized, i.e. the sequence of ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.7.2 DVB-I client behaviour | The DVB-I client can discriminate among the above options by means of the @contentType attribute of UriBasedLocation: • If @contentType attribute carries application/dash+xml, the URL refers to an MPD file, describing either a DVB-I linear service or a playlist generated server side transparently for the DVB-I client. ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.7.3 Handling and end of playlist or VoD content | When the DVB-I client has played out the VoD MPD or all of the items in the playlist, it should present a Content Finished image if one is signalled. A content finished image is signalled in a RelatedMaterial element with the following: • A HowRelated element with an @href attribute carrying the value urn:dvb:metadata:... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.7.4 Examples | a) Description of a DVB-I linear service: <ServiceInstance> <DisplayName>Linear Service 24/7</DisplayName> <DASHDeliveryParameters> <UriBasedLocation contentType="application/dash+xml"> <URI> https://www.broadcaster.com/mpd/linear_service_24x7.mpd </URI> </UriBasedLocation> </DASHDeliveryParameters> </ServiceInstance> ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8 Images | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8.1 Introduction | 5.2. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 8.1 Introduction | Provides an image linked from the content guide sourced metadata and scaled according to the provided width parameter in pixels. Service Lists, services, applications, and programmes may have an associated image, referenced in the ServiceList element, GroupInformation fragment or ProgramInformation fragment within a Re... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8.2 Image Processing Requests | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8.2.1 Image Variants | A range of variants may be available for certain image categories as defined below. If the default variant is not required, the DVB-I client may append an optional image_variant query parameter to requests to certain endpoints to request a particular variant. Only the requested variant, if available for an item, shall ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8.2.2 Image Resolution | The value of RelatedMaterial.MediaLocator.MediaUri shall represent the image_url for the image request. The client may request that the server preform image scaling by using the following query parameter: <image_URL>?w=<width> where: • width is the width in pixels of the requested image. The original aspect ratio of th... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.8.3 Image Response | A Content Guide Server shall return an image of the required dimensions in JPEG or PNG format as specified in clause 7.1.1 of TS 102 796 [21], with the exception that GIF images are not supported. The format shall be specified in the MediaUri@contentType attribute. All images shall meet the following restrictions: • Fo... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.9 Extensibility | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.9.1 Introduction | Certain aspects of the DVB-I Service List Entry Points schema (see clause 5.3) and DVB-I Service List schema (see clause 5.5) are extensable. Rather than the general extensiblity offered through the use of the <any> and <anyAttribute> Wildcard Schema Components defined in W3C XML Schema [i.7], the present document defi... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.2.9.2 Extensibility Base | The ExtensionBaseType defined in clause 5.5.23 is an abstract base type that 3rd parties extend to define concrete data types that can then be used to define elements in the XML instance document. This is a complexType and all 3rd party defined attributes and elements need to be contained within it. The ExtensionBaseTy... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3 Service List Entry Points | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3.1 Service List Entry Point schema | <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:dvbisld="urn:dvb:metadata:servicelistdiscovery:2020" xmlns:mpeg7="urn:tva:mpeg7:2008" xmlns:tva="urn:tva:metadata:2019" xmlns:dvbisd="urn:dvb:metadata:servicediscovery:2020" targetNamespace="urn:dvb:metadata:servicelistdiscovery:2020" elementFormDefault="qualified"... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3.2 ServiceListEntryPoints | An XML instance document containing a ServiceListEntryPoints element is returned on interface F2 in response to a Service List Discovery query (see clause 5.1.3). <element name="ServiceListEntryPoints" type="dvbisld:ServiceListEntryPointsType"/> <complexType name="ServiceListEntryPointsType"> <sequence> <element name="... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3.3 OrganizationType | <complexType name="OrganizationType"> <complexContent> <extension base="mpeg7:AgentType"> <sequence> <element name="Name" maxOccurs="unbounded"> <complexType> <complexContent> <extension base="mpeg7:TextualType"> <attribute name="type" use="optional"> <simpleType> <restriction base="NMTOKEN"> <enumeration value="former... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3.4 ProviderOfferingType | <complexType name="ProviderOfferingType"> <sequence> <element name="Provider" type="dvbisld:OrganizationType"/> <element name="ServiceListOffering" type="dvbisld:ServiceListOfferingType" maxOccurs="unbounded"/> </sequence> </complexType> Table 11: Provider Offering Fields |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.3.5 ServiceListOfferingType | <complexType name="ServiceListOfferingType"> <sequence> <element name="ServiceListName" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="ServiceListURI" type="dvbisd:ExtendedURIType" maxOccurs="unbounded"/> <element name="Language" type="tva:AudioLanguageType" minOccurs="0" maxOccurs="unbounded"/> <eleme... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.4 Schema | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.4.1 Schema Declaration | <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:dvb:metadata:servicediscovery:2020" xmlns:dvbisd="urn:dvb:metadata:servicediscovery:2020" xmlns:mpeg7="urn:tva:mpeg7:2008" xmlns:tva="urn:tva:metadata:2019" elementFormDefault="qualified" attributeFormDefault="unqualified"> <import namespace="urn:tva... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.4.2 Entity Definitions | The following entities are defined in this schema for readability, maintainability and refined faceting. <!DOCTYPE schema [ <!ENTITY PostcodeChar "A-Za-z0-9"> <!ENTITY PostcodeSep "\- "> <!ENTITY Postcode "[&PostcodeChar;]+([&PostcodeSep;][&PostcodeChar;]+)?"> <!ENTITY PostcodeWildFirst "\*[&PostcodeChar;]*[&PostcodeSe... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5 Service Lists | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.1 ServiceList | An XML instance document containing a ServiceList element is returned on interface B2 in response to a service list query. <element name="ServiceList" type="dvbisd:ServiceListType"/> <complexType name="ServiceListType"> <sequence> <element name="Name" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="Prov... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.2 ServiceType | <complexType name="ServiceType"> <sequence> <element name="UniqueIdentifier" type="dvbisd:ServiceIdentifierType"/> <element name="ServiceInstance" type="dvbisd:ServiceInstanceType" minOccurs="0" maxOccurs="unbounded"/> <element name="TargetRegion" type="dvbisd:RegionIdRefType" minOccurs="0" maxOccurs="unbounded"/> <ele... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.3 Convenience Types | |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.3.1 ServiceIdentifierType | <simpleType name="ServiceIdentifierType"> <restriction base="anyURI"/> </simpleType> |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.3.2 SubscriptionPackageType | <complexType name="SubscriptionPackageType"> <simpleContent> <extension base="mpeg7:Textualtype"/> </simpleContent> </complexType> ETSI ETSI TS 103 770 V1.1.1 (2020-11) 48 |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.4 ServiceInstanceType | <complexType name="ServiceInstanceType"> <sequence> <element name="DisplayName" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="RelatedMaterial" type="dvbisd:RelatedMaterialType" minOccurs="0" maxOccurs="unbounded"/> <element name="ContentProtection" type="dvbisd:ContentProtectionType" min... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.5 ContentAttributesType | <complexType name="ContentAttributesType"> <sequence> <element name="AudioAttributes" type="tva:AudioAttributesType" minOccurs="0" maxOccurs="unbounded"/> <element name="AudioConformancePoint" type="tva:ControlledTermType" minOccurs="0" maxOccurs="unbounded"/> <element name="VideoAttributes" type="tva:VideoAttributesTy... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.6 ContentGuideSourceListType | <complexType name="ContentGuideSourceListType"> <sequence> <element name="ContentGuideSource" type="dvbisd:ContentGuideSourceType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> ETSI ETSI TS 103 770 V1.1.1 (2020-11) 51 Table 19: ContentGuideSourceListType Fields Name Semantic Definition Constraints Co... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.7 ContentGuideSourceType | <complexType name="ContentGuideSourceType"> <sequence> <element name="Name" type="mpeg7:TextualType" minOccurs="0" maxOccurs="unbounded"/> <element name="ProviderName" type="mpeg7:TextualType" maxOccurs="unbounded"/> <element name="RelatedMaterial" type="dvbisd:RelatedMaterialType" minOccurs="0" maxOccurs="unbounded"/>... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.8 DVBTripletType | This definition of DVBTripletType is adapted from the DVBTriplet defined in ETSI TS 102 034 [4]. <complexType name="DVBTripletType"> <attribute name="origNetId" type="dvbisd:OrigNetId" use="optional"/> <attribute name="tsId" type="dvbisd:TSId" use="optional"/> <attribute name="serviceId" type="dvbisd:ServiceId" use="re... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.9 ExtendedURIType | A type used to provide a URI with additional information. <complexType name="ExtendedURIType"> <sequence> <element name="URI" type="anyURI"/> </sequence> <attribute name="contentType" type="mpeg7:mimeType" use="required"/> </complexType> Table 22: ExtendedURIType Fields Name Semantic Definition Constraints URI The URI ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.10 LCNTableEntryType | <complexType name="LCNTableEntryType"> <attribute name="channelNumber" type="positiveInteger" use="required"/> <attribute name="serviceRef" type="dvbisd:ServiceIdentifierType" use="required"/> <attribute name="selectable" type="boolean" default="true"/> <attribute name="visible" type="boolean" default="true"/> </comple... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.11 LCNTableListType | <complexType name="LCNTableListType"> <sequence> <element name="LCNTable" type="dvbisd:LCNTableType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> Table 24: LCNTableListType Fields Name Semantic Definition Constraints LCNTable A channel number table representing an ordered sequence of services irresp... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.12 LCNTableType | <complexType name="LCNTableType"> <sequence> <element name="TargetRegion" type="dvbisd:RegionIdRefType" minOccurs="0" maxOccurs="unbounded"/> <element name="SubscriptionPackage" type="dvbisd:SubscriptionPackageType" minOccurs="0" maxOccurs="unbounded"/> <element name="LCN" type="dvbisd:LCNTableEntryType" minOccurs="0" ... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.13 McastType | For semantic and syntax definitions, refer to clause 5.2.12.14 of ETSI TS 102 034 [4]. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.14 RTSPURLType | For semantic and syntax definitions, refer to clause 5.2.12.30 of ETSI TS 102 034 [4]. |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.15 ServiceAvailabilityType | <complexType name="ServiceAvailabilityType"> <sequence> <element name="Period" maxOccurs="unbounded"> <complexType> <sequence> <element name="Interval" minOccurs="0" maxOccurs="unbounded"> <complexType> <attribute name="days" type="dvbisd:ServiceDaysList" default="1 2 3 4 5 6 7"/> <attribute name="recurrence" type="uns... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.16 ServiceDaysList | <simpleType name="ServiceDaysList"> <list> <simpleType> <restriction base="integer"> <minInclusive value="1"> <annotation><documentation xml:lang="en">Monday</documentation></annotation> </minInclusive> ETSI ETSI TS 103 770 V1.1.1 (2020-11) 55 <maxInclusive value="7"> <annotation><documentation xml:lang="en">Sunday</do... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.17 ZuluTimeType | This datatype restricts the xml:time type, permitting only Zulu time to be specified. Zulu time, denoted by "Z" is equivalent to UTC (see clause 3.2.8.2 of W3C XML Schema Part 2: Datatypes [i.6]). <simpleType name="ZuluTimeType"> <restriction base="time"> <pattern value="(([01]\d|2[0-3]):[0-5]\d:[0-5]\d(\.\d+)?|(24:00:... |
a7692028bb2afb42779be7e663d1bc49 | 103 770 | 5.5.18 Delivery Parameters |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.