hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.38 Void | Descriptions of new fixed part tests specific to NG DECT Part 5 start at clause 7.40. This leaves room for tests of features and procedures that may be designed in the future but which are not specific to Part 5. That is, the tests for new features that will apply to both Part 3 and Part 5, because they are considered ... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.39 Void | Descriptions of new fixed part tests specific to NG DECT Part 5 start at clause 7.40. This leaves room for tests of features and procedures that may be designed in the future but which are not specific to Part 5. That is, the tests for new features that will apply to both Part 3 and Part 5, because they are considered ... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.40 TC_FT_GAP.N.1 Outgoing call | The following test cases shall apply. They are summarized in Table 3. Table 19: Summary of contact number matching test cases on FT side Side Call rank Implementation Use Case (note 1) TC number FT First call Early {CC-CONNECT} 1 (if FT_IXIT_22=early) TC_FT_GAP.N.1_BV_102 FT First call Non-early {CC-CONNECT} 1 (FT_IXIT... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.41 TC_FT_GAP.N.8 Incoming call | TC_FT_GAP.N.8_BV_101 {CC-SETUP} crossing management - incoming call from IUT - crossing voice call - incoming call restarted from IUT Test purpose: Test the FT behaviour when: 1- IUT (FT) starts an incoming voice call (initiated from Phone A) 2- Tester (PT) immediately answers with a crossing outgoing voice call 3- Abn... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.42 TC_FT_NG1.N.23 Line and Diagnostic Test Cases | NOTE 1: Test steps are supposed to occur as separated in time as needed so that {FACILITY} messages for different events are not aggregated. NOTE 2: "<<BASIC SERVICE LiA>> IE" is used as a shortcut for "<<BASIC-SERVICE>> IE Call class = LiA service setup, Basic service = Wideband speech default setup attributes". TC_FT... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 7.45 TC_FT_NG1.N.26 DTAM Screening Test Cases | TC_FT_NG1.N.26_BV_101 Call screening indication and release from FT Test purpose: Test that FT sends call screening indication (CS screening setup) to the PT (set as screening PT for the used DTAM) and releases the call to PT after 'Screening acceptance timeout' 1-Incoming call from Phone A presented until DTAM timeout... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 1 Scope | The present document is the seventh document of a series of "S-documents" produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and s... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 3 Definitions and abbreviations | |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: baseline: minimum set of functions that should be implemented to be compliant with TV-Anytime Forum specifications ETSI ETSI TS 102 822-7 V1.1.1 (2003-10) 8 bi-directional network: network that supports two way, point-to-point, one-to-... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard ASN.1 Abstract Syntax Notation. One CA Certificate Authority CRL Certificate Revocation List DER Distinguished Encoding Rules DES Data Encryption Standard DH Diffie-Hellman DHE Ephemeral Diffie-Hellman DSS Digi... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 4.1 TLS Protocol (informative) | |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 4.1.1 Overview | The TLS protocol version 1.0 [7] is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol. At the lowest level, layered on top of some reliable transport protocol (e.g., TCP), is the TLS Record Protocol. The TLS Record Protocol provides connection security that has two basic properties: Secrecy... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 4.1.2 Handshake | A connection is divided into two phases, the handshake and data transfer phases. The handshake phase authenticates the server and establishes the cryptographic keys which are used to protect the data to be transmitted. The handshake must be completed before any application data can be transmitted. The purpose of the ha... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 4.2 Advantages of TLS | Advantages of TLS are: 1) Cryptographic security: TLS is a matured and well-deployed security protocol. 2) Extensibility: TLS provides a framework into which new public key and bulk encryption methods can be incorporated as necessary. 3) Application protocol independency: Higher level protocols can layer on top of the ... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1 TLS Cipher suites | |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1.1 Pre-Master Key Delivery | A TV-Anytime TLS implementation shall use Diffie-Hellman key agreement and should generate new Diffie-Hellman key pairs at both sides for each instantiation of the TLS handshake protocol. This is commonly called an Ephemeral- Ephemeral Diffie-Hellman exchange. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1.2 Digital Signature Algorithm | The algorithm shall be RSA. The RSA key size shall be at least 1 024 bits. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1.3 MAC (Message Authentication Code) Algorithm | The algorithm shall be HMAC-SHA1 [6]. The key for HMAC-SHA1 shall be 160 bits. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1.4 Cipher Algorithm | The required algorithms shall be both NULL encryption and AES. IETF defines a separate RFC for use of AES with TLS [8]. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.1.5 TLS Cipher suites | A TV-Anytime compliant application shall implement the cipher suites TLS_DHE_RSA_WITH_NULL_SHA and TLS_DHE_RSA_WITH_AES_128_CBC_SHA. Cipher Suite Key Exchange Signature Cipher Hash TVA Status TLS_DHE_RSA_WITH_NULL_SHA DH RSA NULL SHA1 Required TLS_DHE_RSA_WITH_AES_128_CBC_SHA DH RSA AES SHA1 Required TLS_DHE_RSA_WITH_C... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2 Certificate Profile | The complexity of X.509 certificates is understood, but X.509 is required for standard TLS implementation. The certificate profile shall comply with RFC 3280 [9]. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1 Certificate Trust Hierarchy | The required Certificate Trust Hierarchy is illustrated in figure 3: Root CA Root CA Metadata Provider CA Metadata Provider CA Web Server CA Web Server Certificate Metadata Provider CA Metadata Provider CA Web Server CA Web Server Certificate Root CA Root CA Root CA Root CA (Root certificate embedded in TVA device) Fig... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.1 TV-Anytime X.509 Certificate Profile Version | The version of the certificates shall be V3. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.2 Public Key Type | Within X.509 certificates, a public key is defined as: SubjectPublicKeyInfo ::= SEQUENCE { algorithm AlgorithmIdentifier, subjectPublicKey BIT STRING } ETSI ETSI TS 102 822-7 V1.1.1 (2003-10) 13 AlgorithmIdentifier ::= SEQUENCE { algorithm ALGORITHM.&id ({SupportedAlgorithms}), parameters ALGORITHM.&Type ({SupportedAlg... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.3 RSA Public Keys | The SubjectPublicKeyInfo algorithm Object Identifier (OID) is: 1.2.840.113549.1.1.1 (rsaEncryption). An AlgorithmIdentifier for an RSA public key does not have any parameters. The RSA public key is represented in ASN.1 as: RSAPublicKey ::= SEQUENCE { modulus INTEGER, -- n publicExponent INTEGER -- e } The RSAPublicKey ... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.4 Extensions | The following five extensions shall be used as specified in the sections below. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.4.1 subjectKeyIdentifier | The subjectKeyIdentifier extension shall be included in all CA certificates. This extension shall include the keyIdentifier value composed of the 160-bit SHA1 hash of the value of the BIT STRING subjectPublicKey (excluding the tag, length and number of unused bits from the ASN1 encoding). This extension shall be marked... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.4.2 authorityKeyIdentifier | The authorityKeyIdentifier extension shall be included in all certificates, with the exception of the root certificate and shall include a KeyIdentifier value that is identical to the subjectKeyIdentifier in the issuing CA certificate. This extension shall be marked as non-critical. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.4.3 keyUsage | The keyUsage extension shall be used in all CA certificates and shall be marked as critical with a value of keyCertSign and cRLSign. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.4.4 basicConstraint | The basicConstraint extension shall be used in all CA certificates and shall be marked as critical. |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.5 Signature Algorithm | The signature mechanism used shall be SHA-1 with RSA Encryption. The specific OID is 1.2.840.113549.1.1.5 and the signature parameters listed in the signed certificate are NULL. ETSI ETSI TS 102 822-7 V1.1.1 (2003-10) 14 |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.1.6 SubjectName and IssuerName | When an X.500 attribute value contains characters that fall entirely within the character set utilized by PrintableString, the ASN.1 type PrintableString shall be used. In all other instances, UTF8String shall be used. When encoding an X.500 Name: 1) Each RelativeDistinguishedName (RDN) shall contain only a single elem... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.2 Certificate Chain Validation Requirements | The certificate chain validation shall comply with RFC 3280 [9]. Additional TVA requirements are: • Verify the extended key usage of the web server certificate with the value as specified • Verify the OU= attribute inside the X.500 names to be "TVA" (without quotes). |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.3 (Metadata) Web Server Certificate Profile | Web Server Certificate Intended Usage For TLS server certificates, where the server is capable of delivering TVA metadata. Version V3 Serial Number Unique value for the given certificate issuer Signature Sha1WithRSAEncryption (OID: 1.2.840.113549.1.1.5) Signed By Metadata provider CA Validity Period Based on policy, no... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.4 Metadata Provider CA Certificate | Metadata Provider CA Certificate Intended Usage To issue web server certificates and CRLs. Version v3 Serial Number Unique value for the given certificate issuer Signature sha1WithRSAEncryption (OID: 1.2.840.113549.1.1.5) Signed By TVA Root CA Validity Period Based on policy. Subject Name Form (open) C=<country code> O... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.5 TV-Anytime Root CA | The TV-Anytime Root CA is currently undefined and in the future may be defined within a different standards body. TV- Anytime places the following requirements on a Root CA: 1) The RSA key size shall be at least 2 048 bits. 2) The private key should be protected using FIPS 140-2 Level 3 (or above) physical security. 3)... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.2.6 Certificate Revocation | Certificate revocation is a critical and at the same time operationally complex part of PKI (Public Key Infrastructure). In the case that a public/private key pair is compromised (e.g., stolen) or in some cases if a business contract that was signed to obtain a certificate has been violated, a certificate needs to be r... |
0e56c1e0c2b9c3ef89dea56904ba3140 | 102 822-7 | 5.3 Device requirements | Each device receiving metadata shall include TVA-defined root CA certificates in order to validate the server's certificate chain. It is to be determined whether there will be more than one Root Certification Authority and if root CAs will be defined and/or operated by TVA or by other standards organizations. The TLS p... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 1 Scope | The present document defines the functional and technical characteristics applicable to the Optical External Network Test Interface (ENTI) terminated with Singlemode fibre which provides testing capability at the demarcation point between the line of the FTTH operator's network and the customer's cabling inside the hou... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 2 References | |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 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... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 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... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 3 Definition of terms, symbols and abbreviations | |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 3.1 Terms | For the purposes of the present document, the following terms apply: cable element: smallest construction unit in a cable EXAMPLE: Cable subassembly comprising one or more optical fibres inside a common covering. distribution space: space within a home that corresponds to the installation space IS4 or IS5 of EN 50491-6... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 3.2 Symbols | Void. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: APC Angled Physical Contact EN European Norm ENTI External Network Test Interface FITH Fibre In The Home FTTH Fibre To The Home IP Ingress Protection LSPM Laser Source Power Meter ETSI ETSI TS 102 873 V1.2.1 (2022-04) 8 OAP Operator Access Poi... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4 Functional characteristics | |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.1 Generalities | Optical ENTI is the physical point at which a subscriber is provided with access to an operator's optical communications network. An ENTI device will be installed for each subscriber. Optical ENTI unit is enclosed in a durable housing appropriate for use in a distribution space and constitutes integral part of the subs... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.2 Optical ENTI location | ENTI, as it is described in the present document for new homes, will be located inside a distribution space (collocated near the home distributor as depicted in figure 2). Optical ENTI characteristics for use outside a distribution space in existing homes are not considered in the present document. Figure 2: Optical EN... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3 Optical termination | |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3.1 Optical termination components and requirements | Optical termination is accomplished by means of fibre optic connector plug and adaptor. The termination of the fibre is a connector plug. The connector plug can be pre-terminated (pre-terminated cable) at the manufacturer's plant or by means of field mountable connector system. Connector plug is positioned in the adapt... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3.2 Pre-terminated connectors as pigtails | A pigtail is a product configuration consisting of a piece of cable terminated with connector on one end. It is a classical solution comprising fibre splicing: • fusion splice; • mechanical splice. Considering 3 additional re-splicing and reconfigurations 0,8 m of fibre overlength shall also be stored. Splice protector... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3.3 Field mountable, pre-terminated connectors with fibre stub | Pre-terminated connector with fibre stub is a product configuration consisting of terminated connector and a small length of fibre (stub) stored within connector body. Termination of the cable with connector can be accomplished by fusion or mechanical splice. Fusion splicing requires special splicing machines. Mechanic... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3.4 Pre-ferruled cables | Pre-terminated cables with pre-ferruled connector plugs are semi terminated drop fibres. The cable is pre-ferruled at least at one end. The connector body can be mounted after pre-terminated cable is installed in the customer technical room/space. The other end can be terminated with connector. This would remove the ne... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.3.5 Pre-terminated cables | Pre-terminated cables with pre-terminated connector plugs are terminated drop fibres. The cable is pre-terminated at least at one end. This would remove the need for splicing in the final drop or in the customer's premises and significantly reduce the cost and skill-set required for installation and maintenance of the ... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.4 Optical measuring and testing features | The measuring features shall allow all optical measurements mainly measurements of attenuation and return loss. Measuring features shall allow attenuation and return loss measurements for both OTDR (Optical Time Domain Reflectometer) and LSPM (Laser Source Power Meter). ETSI ETSI TS 102 873 V1.2.1 (2022-04) 11 |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.5 Connection to ONT | Optical Network Termination (ONT) is connected to ENTI by means of optical terminated cord. Optical terminated cord is a product defined as a fibre optic cable terminated with connector on both ends. Connectors terminated on cord shall be of the same type as in optical ENTI and ONT. Hybrid patchcords are possible. Conn... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.6 Optical ENTI outlet | The parts of the optical ENTI outlet besides connector and adaptor are: • outlet having facilities to be fastened inside technical room; • means for incoming cables; • fibre tray with guiding and storage elements; • allow fibre bend radius of 15 mm for fibres according to EN 60793-2-50 [3] category B6. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 4.7 Opening and prevention of damaging of outlet and fibre | • Using a screwdriver by unskilled people shall not cause irreversible damage of the outlet. • If the outlet is accidentally opened the forces to the fibre shall be below fibre damaging levels. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5 Particular characteristics | |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.1 Environmental conditions | The environmental conditions of the materials which are installed inside customer's premises are those applicable to the equipment of telecommunications in service, at fixed station, in sites protected from the bad weather, at partially controlled temperature: clause 3.2 of ETSI ETS 300 019-1-3 [12]. The environmental ... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.2 Laser safety | Due to the potentially increased hazards arising from higher optical powers, additional user information may be needed. The safety measures to protect against effects caused exclusively by thermal, optomechanical and related effects in passive optical components and optical cables shall be accomplished. The internation... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.3 Installation and dimensioning | The ENTI outlet is designed: • To have an attachment unit allowing horizontal/vertical adjustment (EN 50174-2 [1]). • No specific tools for installation. • To ensure a protection against wet wall effects. ETSI ETSI TS 102 873 V1.2.1 (2022-04) 12 • To allow minimum fibre bending radius of 15 mm for fibres according to E... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.4 Fibre types | The fibre types for the cables and connectors shall be according to EN 60793-2-50 [3], categories B1.3 or B6_a fibre. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.5 Fibre splices | Fibre splices shall be either mechanical splices according to EN 61753-131-3 [10] or fusion splices according to ETSI TS 100 783 [11]. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.6 Fibre optic connectors | Fibre optic connectors at ENTI shall conform to EN 50377 series [2]. Following functionalities of the connector should be considered: • Protection class: IP 54. • Crimped strain relief connector. • Cost optimized. • Dust protection. • Eye protection. • Ferrule protection (within the shape of connector). • Optimized len... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.7 Optical cables to be installed in ENTI outlet | Cable requirements in ENTI shall cover all three optical cable possibilities defined in standardization documents: • Loose tube outdoor cable types (EN 60794-3-10 [7] and EN 60794-3-11 [8]). • Breakout indoor cable types (EN 60794-2 [4] and EN 60794-2-20 [5]). • Optical self-supporting aerial cable (EN 60794-3-20 [9]).... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.8 Measuring or monitoring of the optical line | The ENTI is designed to allow the following tests: • To be able to measure the optical attenuation of the line at the connection of the access cable and at the connection of the customer's cable(s). • To be able to measure the optical reflection of the line at the connection of the access cable and at the connection of... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.9 Measurements with OTDR | The measuring procedure is defined in EN 61280-4-2 [18]. If OTDR is used for the measurements of the optical line following aspects shall be considered: • use of the launch and tail test cord; • bidirectional measurements as reference method; • unidirectional measurements with increased measurement uncertainty. The bid... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.10 Measurements with LSPM | The measuring procedure is defined in EN 61280-4-2 [18], one-cord reference method. This method uses optical power measurement equipment consisting of: 1) Light source 2) Test cords 3) Power meter The results of this measuring method deliver an absolute attenuation value of the link without any evaluation of the occurr... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.11 Operations | Following aspects shall be covered prior to any removing of the ENTI housing cover or measuring as well as reconfiguring actions: • Instructions should be provided to personnel handling connectors in optical systems. • Cleanliness of the connectors is very important. • Appropriate measuring cords shall be used. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.12 Miscellaneous | The appropriate marking for laser devices according to IEC 60825-2 [17] shall be visible on the ENTI housing. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.13 Documentation | In each package of ENTI, documentation should be provided including a technical note of installation and a technical note of operation and maintenance. |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 5.14 Recycling | The ENTI is designed: • To limit the number of components and materials. • To support the concept facilitating the recycling of materials. • To provide the indications necessary for the recycling of the material at the end of the lifetime. • To provide a mechanical protection of the connector industry (case). • To resp... |
969490d00e2eefdb8963f17cd5a45c48 | 102 873 | 6 Testing | The purpose of the tests described hereafter, applicable to optical ENTI or outlet are to approve all transmission, environmental and mechanical requirements specified in the present document. Table 1: Tests applicable to optical ENTI and housing Tests required Standards or Specifications Requirements Visual inspection... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 1 Scope | The present document is the sixth in a series of specification documents produced by the TV-Anytime Forum. These documents establish the fundamental specifications for the services, systems and devices that will conform to the TV-Anytime standard, to a level of detail that is implementable for compliant products and se... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 3 Definitions and abbreviations | |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: acquisition: retrieval of content application: specific set of functions running on the PDR NOTE: Some applications use metadata, either automatically or under consumer control. authority: organization that creates CRIDs bi-directional... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARIB Association of Radio Industries and Businesses NOTE: A Japanese standards organization. ATSC Advanced Television Systems Committee NOTE: American based standards organization for establishing technical standards for advanced television sy... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4 Introduction | The TV-Anytime Forum has defined a number of data types that can be exchanged between TV-Anytime devices. These include programme metadata, content referencing information, and user-centric metadata. The present document is concerned with data exchange between TV-Anytime clients and metadata servers over a bi-direction... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.1 Types and functionalities of Metadata services | TV-Anytime metadata services can be broken into two basic types, which are shown in figures 2 and 3. The metadata services specified are all request-response based. This can be seen in the two figures - the network transaction is always point-to-point (client to server), and the transaction is always initiated by the c... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.1.1 Metadata retrieval | Metadata retrieval occurs when a client wishes to obtain certain metadata from a metadata service that it has previously discovered and obtained a capability description for. The following list gives some examples of metadata retrieval: • A client wishes to obtain programme reviews for a CRID. The client sends a reques... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.1.2 Submission of user-centric metadata | Submission of user-centric metadata offers a number of possible benefits to both consumers and metadata service providers. These are described in clause 5 of TS 102 822-3-1 [4]. Ensuring the privacy of these transactions and that the metadata service provider is trustworthy is essential to the submission of user-centri... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.2 Metadata service capability descriptions | In order to exploit usefully the metadata services described in the previous clause, the client needs information about the nature of the metadata service being offered. This is because different metadata services will provide different types of metadata and can be queried in different ways. For example, some metadata ... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.3 Metadata service discovery | Metadata service discovery is the process by which a client establishes a URL where a TV-Anytime metadata service can be found. There are a number of ways this process can occur, but only the third method (see clause 4.3.3) is addressed by the present document. |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.3.1 Non-standardized discovery | A number of methods exist for discovering the URLs of metadata services that will not be standardized by the TV-Anytime Forum. The following list gives some examples: • The client might be pre-programmed with a set of URLs that refer to one or more metadata services. This will typically be useful in a vertical market, ... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.3.2 Unidirectional delivery of discovery information | The System Specification [13] and Content Referencing Specification [8] define ways or requirements on the underlying transport, in which the URL of a bi-directional metadata and/or content referencing service can be discovered from TV-Anytime information inserted in a unidirectional stream. The present document define... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 4.3.3 Client-Initiated discovery using the bi-directional network | This mode of metadata service discovery involves using the bi-directional network to access a "Yellow Pages" of TV-Anytime metadata services. The mechanism is based upon W3C standards for web service discovery (UDDI [16] and WS-Inspection [17]), the use of which is standardized by the TV-Anytime Forum, according to the... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5 Metadata service discovery | The present document describes how standard web service discovery techniques can be used to allow PDRs and other TV-Anytime clients to discover TV-Anytime metadata services. The relevant standards are UDDI [16] and WS-Inspection [17], which enable different, but complementary, modes of discovery. A provider can choose ... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2 Universal Description, Discovery and Integration (UDDI) | UDDI [16] allows PDRs, and other clients with Internet connectivity, to discover TV-Anytime metadata services without the client requiring any prior knowledge of the metadata service, nor any information from a unidirectional metadata service. Metadata service providers may publish details of their TV-Anytime metadata ... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.1 TV-Anytime web service tModels | These tModels are used when a business publishes details of their bindingTemplate structures to indicate a web service compliant with the present document. Clients issuing UDDI inquiry requests can use these two tModel keys to find only web services that are TV-Anytime metadata services. |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.1.1 TV-Anytime get_Data port tModel | This technical model represents a get_Data port as described in clause 5.1. Name: TV-Anytime-org:get_Data_v10. Description: TV-Anytime WSDL interface for get_Data port. UDDI Key (V3): uddi:TV-Anytime.org:get_Data_v10. Categorization: specification, xmlSpec, soapSpec, wsdlSpec. <tModel tModelKey="uddi:TV-Anytime.org:get... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.1.2 TV-Anytime submit_Data port tModel | This technical model represents a submit_Data service as described in clause 5.2. Name: TV-Anytime-org:submit_Data_v10. Description: TV-Anytime WSDL interface for submit_Data port. UDDI Key (V3): uddi:TV-Anytime.org:submit_Data_v10. Categorization: specification, xmlSpec, soapSpec, wsdlSpec. ETSI ETSI TS 102 822-6-2 V1... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2 TV-Anytime categorization tModels | These tModels allow a metadata service provider to categorize their services. The metadata service provider assigns the categories at the point of publication (see clause 5.2.3). This enables clients to issue more refined UDDI searches for metadata services. By categorizing a metadata service as richly and accurately a... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2.1 TV-Anytime authorityName categorization system | The authorityName tModel is used to represent the resolution authorities of the CRIDs for which this metadata service provides TV-Anytime information. To establish whether content referencing information or metadata is available for the authority, the tableType tModel may be used (see clause 5.2.2.2). Name: TV-Anytime-... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2.2 TV-Anytime tableType categorization system | The tableType tModel is used to represent the types of metadata table that this metadata service is capable of providing. Name: TV-Anytime-org:tableType. Description: Category system for the metadata table types available from a metadata service. UDDI Key (V3): uddi:TV-Anytime.org:tableType. Valid values: A valid value... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2.3 TV-Anytime serviceURL categorization system | The serviceURL tModel is used to represent the content delivery services (e.g. channels) for which this metadata service provides TV-Anytime information. Name: TV-Anytime-org:serviceURL. Description: Category system for the content services handled by a metadata service. UDDI Key (V3): uddi:TV-Anytime.org:serviceURL. V... |
e6d0d4822c5f17f4f79a5c16bea025f1 | 102 822-6-2 | 5.2.2.4 TV-Anytime genre categorization system | The genre tModel is used to broadly classify the types of programmes for which this metadata service provides TV-Anytime information. This tModel is intended to classify metadata services providing specialist information, and will not be useful for metadata services that describe a wide range of programme types (e.g. b... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.