hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.2 Manifest and Repository Convention | The NIP bootstrap stream carries a single Content Protection Assets Signalling Manifest carrying the information for all content protection solution providers and their assets required for protected services broadcast on the current physical or commercial network. The Content Protection Assets Signalling Manifest shall... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.3 Content Protection Assets Signalling Manifest | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.3.1 Structure | The Manifest document is structured according to the content protection solution provider unique identifier. This identifier shall correspond to the CP System ID registered at DVB Services Sàrl. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.3.2 Multicast Transport Session Identifiers | 10.3.1.3.2.1 @ServiceClass For the Content Protection Assets Signalling Manifest and all the content listed in the Manifest itself, the @serviceClass as introduced in clause 9.5.2.1 shall be: urn:dvb:metadata:nativeip:ContentProtectionAssets 10.3.1.3.2.2 @Tags The Content Protection Assets Content @tags (URI) links the... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4 Content Protection Assets Signalling Manifest Schemas | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4.1 Content Protection Assets Signalling Manifest Schema Declaration | <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:dvb:metadata:nativeip:2023" xmlns="urn:dvb:metadata:nativeip:2023" elementFormDefault="qualified"> <xs:element name="ContentProtectionAssetsSignallingManifest" type="ContentProtectionAssetsSignallingManife... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4.2 ContentProtectionAssetsSignallingManifestType | <xs:complexType name="ContentProtectionAssetsSignallingManifestType"> <xs:sequence> <xs:element name="VersionUpdate" type="xs:dateTime" /> <xs:element name="ContentProtectionProvider" type="ContentProtectionProviderType" minOccurs="1" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> Table 10.3.1.4.2-1: Content... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4.3 ContentProtectionProviderType | <xs:complexType name="ContentProtectionProviderType"> <xs:sequence> <xs:element name="ContentProtectionAssetsSession" type="ContentProtectionAssetsSessionType" minOccurs="1" maxOccurs="unbounded" /> </xs:sequence> <xs:attribute name="contentProtectionProviderID" type="CP_System_ID" use="required" /> <xs:simpleType name... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4.4 ContentProtectionAssetsSessionType | <xs:complexType name="ContentProtectionAssetsSessionType"> <xs:sequence> <xs:element name="VersionUpdate" type="xs:dateTime" minOccurs="0" /> <xs:element name="TagRef" type="xs:anyURI" minOccurs="1" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> Table 10.3.1.4.4-1: ContentProtectionAssetSessionType Fields Na... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.4.5 Content Protection Assets Signalling Manifest Example | <?xml version="1.0" encoding="UTF-8"?> <ContentProtectionAssetsSignallingManifest xmlns="urn:dvb:metadata:nativeip:2023" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:dvb:metadata:nativeip:2023 content_protection_assets_signalling_manifest.xsd"> <VersionUpdate>2023-12-28T17:06:33Z</Versi... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.5 Receiver Implementation Guideline | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.5.1 NIP Gateway | The Content Protection Assets Manifest shall be broadcast on the bootstrap NIP stream(s) of the technical operator or commercial operator network, as specified in clause 8.2.5.1. Each time the NIP Gateway tunes to the bootstrap NIP stream, it shall search for the presence of a Content Protection Assets Signalling Manif... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.1.5.2 Content Protection Solution Application and NIP Gateway Interaction | • The content protection solution application sends an http GET request to the NIP Gateway for the Content Protection Assets Signalling manifest: /nip-cpa-manifest.xml • The content protection solution application parses the manifest document and makes a query to the DVB Gateway for the selected <TagRef>. EXAMPLE 1: dv... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 10.3.2 MPEG Transport Stream Encryption | DVB-NIP A/V content broadcast using DVB-MPE encapsulated NIP Streams may be protected using DVB-CSA. The workflow to signal and provide Entitlement Management Message (EMM) and Encrypted Control Messages (ECM) shall comply to DVB-CSA and DVB-SI (ETSI EN 300 468 [14]). This solution will provide transport level security... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11 Deployment Specific Protocols | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1 NIP Gateway Announcement and Discovery Protocol | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.1 Introduction | Consumer NIP Gateways according to DM3 shall support DNS-SD/mDNS as network device discovery protocol. This guarantees that network clients can easily discover the presence of a NIP Gateway on the local network and discover the services provided by the NIP Gateway. NIP clients shall support the DNS-SD/mDNS Network Devi... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.2 DNS-SD/mDNS | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.2.1 General | The method described in the present clause is intended to be applicable in DVB-NIP and DVB-HB [13] contexts. In particular, the term DVB Gateway indicates a device which may provide functions of a DVB-NIP Local Server as defined in the present document, a DVB-HB Gateway as defined in DVB-HB [13], or both. ETSI ETSI TS ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.2.2 Pointer Record (PTR) | The PTR record is used to point clients looking for a DNS-SD service to the devices providing that service. The PTR record format is as follows: <Service Type>.<Domain> <TTL> PTR <Instance Name>.<Service Type>.<Domain> where: <Service Type> is the combination of a standard IP protocol name and a transport protocol name... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.2.3 Service Record (SRV) | The SRV record has the following structure, as defined in IETF RFC 6763 [18] and IETF RFC 2782 [24]: <Instance Name>.<Service Type>.<Domain> <TTL> IN SRV <Priority> <Weight> <Transport Port> <IP addres s> It associates the name of a service (structured as <Instance Name>.<Service Type>.<Domain>) with the IP address and... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.1.2.4 Text Record (TXT) | The TXT record is intended to convey a small amount of useful additional information about a service. It is a concatenated list of "key=value" pairs separated by semicolons, with the following structure: <Instance Name>.<Service Type>.<Domain> <TTL> TXT "<key_1>=<value_1>[;<key_n>=<value_n>]" Available keys for the TXT... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.2 Professional Edge Cache Receiver Configuration | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 11.2.1 Control API | A REST Control API for professional Edge Cache Receivers will be provided in a subsequent version of the present document. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 88 Annex A (normative): Transport Stream based Carriage A.1 Introduction Receivers deployed with hardware that cannot be upgraded to the use of GSE-Lite accord... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 1 Scope | Internet protocol is the most common protocol for communicating between devices, hosts and back-end systems in modern network environments. Internet-of-Things (IoT) is the integration of various devices to the Internet, enabling data collection and device control in various systems. DECT-2020, especially in mesh networ... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 2 References | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 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... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 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... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 3 Definition of terms, symbols and abbreviations | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 3.1 Terms | For the purposes of the present document, the terms defined in ETSI TS 103 636-1 [1] and the following apply: Backend Router (BAR): connects DECT-2020 Border Routers to internet Border Router (BR): connects the DECT-2020 radio network to internet or Backend Router end-point: Internet host communicating with an RD in DE... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 3.2 Symbols | Void. |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 636-1 [1] and the following apply: BAR Backend Router BR Border Routers ETSI ETSI TS 103 874-3 V1.2.1 (2026-01) 8 CDD Configuration Data Distribution DNS Doman Name Service DNS-SD Doman Name Service - Service Discovery DTLS Datagram Transp... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4 General | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1 Introduction | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1.1 General | The present document defines how IPv6 [4] transmissions and addressing is done in the DECT-2020 New Radio (NR) [1]. MAC DLC CVG Application Application IPv6 PHY RD1 (PT mode) Transmission service Security service Transmission service MUltiplexing service Routing service DLC entity set MAC DLC CVG Application Applicatio... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1.2 DECT-2020 addressing usage | IPv6 addressing is not used for the routing of messages inside the DECT-2020 network. It is expected that a border router, that connects the DECT-2020 radio network to Internet, can map the IPv6 addresses to device RD Long IDs used in routing on the DLC layer, and can then either perform route discovery as defined in i... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1.3 No detailed DECT-2020 stack configuration | IPv6 Profile defines the IPv6 operation over DECT-2020. IPv6 is not a specific application but itself a generic communication protocol stack. It can run on top of various DECT-2020 stack configurations, for example over long latency massive mesh networks or over low latency star networks. Other application profiles def... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1.4 IPv6 DECT-2020 CVG endpoint | DECT-2020 convergence layer (CVG) [3] defines application, or endpoint, multiplexing for DECT-2020 networks. A CVG endpoint multiplexing identifier has been defined for IPv6 in https://portal.etsi.org/PNNS/Protocol-Specification- Allocation/DECT-2020-NR-Endpoint-Multiplexing-Addresses. Separate endpoints have been defi... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.1.5 Configuration data distribution | IPv6 profile address autoconfiguration and optimizations rely on Configuration Data Distribution (CDD) [3]. |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.2 Services expected of DECT-2020 CVG and DLC layer | IPv6 profile expects following services from DECT-2020 stack [2] and [3]: • Transmission and reception of CVG PDUs • Support 1280-byte IPv6 Packets in CVG payload • Reliable transmissions • DECT-2020 DLC routing of transmissions to destination devices using the DECT Long RD ID • Long RD ID addressing information for re... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 4.3 Order of transmission | The transmission order is Big endian and left to right: • A list of octets is transmitted 1st octet first. ETSI ETSI TS 103 874-3 V1.2.1 (2026-01) 10 • For each octet, bits are numbered 0 to 7 according to transmission order. Bit 0 is transmitted first (ascending transmission order). • This order is the same as defined... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5 IPv6 protocol adaptation definition | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.1 General | IPv6 adaptation for DECT-2020 is defined to ensure the fluent operation of IPv6 and related Internet protocols over the varying link capacities encountered in the DECT-2020 networks. Especially in a DECT-2020 mesh network the link capacity can vary greatly as an IPv6 packet is transmitted hop-by-hop to the destination ... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.2 IPv6 addressing architecture | The DECT-2020 mesh is a mesh-under routing network, so the link-local IPv6 addresses are not scoped to the next DECT-2020 radio hop but extend over all the radio links in a DECT-2020 network as shown in Figure 5.2-1. Network always has a Border Router, with one or more Sinks. Network may have multiple Border Routers un... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.3 IPv6 link maximum transmission unit | IPv6 requires link MTU to be at least 1 280 bytes [4]. RDs shall support link MTU of at least 1 280 bytes as CVG payload. The DECT-2020 CVG and DLC layers [3] shall fragment and reassemble packets forwarded over DECT-2020 network. |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.4 IPv6 prefix configuration | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.4.1 IPv6 address allocation options to routers | The addressing scope and Internet side address configuration mechanism how a BAR or BR receives an internet address is not defined in the present document. Internet protocols provide multiple locally configurable options for address allocation. The BAR can receive a DECT-2020 network prefix explicitly with prefix deleg... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.4.2 Prefix advertisement for DECT-2020 RDs | Devices shall create unique IPv6 addresses based on shared Prefix as published by the Sink and with the IID part consisting of DECT-2020 Sink Long RD ID and the device's own Long RD ID [2]. ETSI ETSI TS 103 874-3 V1.2.1 (2026-01) 12 RDs shall support Configuration Data Distribution (CDD) [3] as defined in Annex A. The ... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.5 Replaced IPv6 procedures | Due to the specific nature of the DECT-2020 network and its services, following IPv6 procedures [4] are not needed for network and communication operation: • Duplicate address detection • Neighbour advertisement or solicitation • Router advertisement or solicitation Addressing inside the DECT-2020 network is based on u... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.6 IPv6 header compression | IPv6 header can be considerable overhead for small link-layer packets. As the link capacity over a weak radio link can be limited, the devices may support header compression as defined in IETF RFC 6282 [7]. Devices shall always support uncompressed IPv6. The BR may be configured to use IPv6 header compression. Header c... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.7 Multicast IPv6 | Multicast routing from backend system into DECT-2020 network and vice versa shall be performed by the BR if configured in IPv6 routing table. RD devices may support IPv6 multicast. It is expected that the IPv6 multicast is static in nature where a BR is configured to forward known IPv6 multicasts and RD devices are pre... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.8 Internet Control Message Protocol (ICMPv6) | The RDs should support ICMPv6 [9] error messages when received as responses for RD initiated transmissions. NOTE 1: RDs in FT mode cannot generate destination unreachable -errors or time exceeded -errors as they only forward the transmissions on DECT-2020 level, not as IPv6 routing forwarding. The RDs should understand... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.9 Transport protocols | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.9.1 General | The RDs shall support UDP [10]. The RDs may support transmission and reception of UDP header compression as defined in IETF RFC 6282 [7]. NOTE: Due to the unreliable nature of UDP, application layer acknowledgements and re-transmissions should be used. Due to the variation on DECT-2020 networks' latency behaviour the p... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.9.2 Transport layer security | DTLS over UDP should be supported. If supported, the RDs shall support DTLS version 1.2 [12]. To optimize DTLS operation for RD whose IPv6 address may change in mesh network self-configuration or node mobility, the DTLS connection ID [13] should be supported by Devices and backend DTLS connection end-points. If TCP is ... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 5.10 DNS and DNS based service discovery | DNS may be supported [17]. DNS service's IPv6 address may be configured using CDD as defined in Annex A. BR or BAR may act as DNS based service discovery proxy [18] for local services. If DNS service discovery is supported, BR or BAR should support unicast DNS-SD and BRs should support multicast mDNS [19]. RDs supporti... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6 Procedures | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.1 Unicast procedures | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.1.1 RD originating unicast transmission procedure | When transmitting a unicast IPv6 packet, IPv6 adaptation layer in an RD shall: • if the destination IPv6 address prefix is the link-local prefix: - set the EP address of the CVG layer to value indicating plain IPv6; - set the CVG layer payload to contain the IPv6 packet; - set the DLC destination address to be the Long... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.1.2 BR originated unicast transmission procedure | When transmitting a unicast IPv6 packet to DECT-2020 network, IPv6 adaptation layer in a BR or Sink shall: • if the destination IPv6 address prefix is the link-local prefix or if the destination IPv6 address prefix is one of the subnet prefixes configured to the BR: - set the EP address of the CVG layer to value indica... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.1.3 Unicast error situations | For source routing and cached routing, the BR may generate ICMPv6 error message destination unreachable based on the DLC Route Error IE it receives, clause 5.3.3.6 of ETSI TS 103 636-5 [3]. |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.2 Multicast procedures | |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.2.1 RD multicast listener registration procedure | When interested in listening to a IPv6 multicast address, and MLDv2 usage is enabled, an RD shall generate an Unsolicited Report for the multicast address listened to as defined in IETF RFC 768 [10]. MLDv2 report transmission should be repeated a few times, with moderate length random delays between transmissions (0 to... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.2.2 RD originated multicast transmission procedure | When transmitting an IPv6 multicast packet, IPv6 adaptation layer in an RD shall: • if the destination IPv6 address scope is larger than link-local scope: - if compressed IPv6 if supported by BR: set the EP address of the CVG layer to value compressed IPv6; compress the IPv6 header; - else: set the EP address of ... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.2.3 BR originated multicast transmission procedure | When transmitting an IPv6 multicast packet to DECT-2020 network, IPv6 adaptation layer in a BR shall: • if there are IPv6 multicast listeners registered for this multicast address: - set the EP address of the CVG layer to value indicating plain IPv6 or compressed IPv6; - set the CVG layer payload to contain the IPv6 pa... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.3 Limiting IPv6 multicast forwarding in DECT-2020 Network | Considering the DECT-2020 Network as single link places specific considerations for having multiple BRs forwarding multicast to the network. If majority of devices are interested in the multicast(s), the IPv6 multicast forwarding should be configured manually in the BRs and MLDv2 operation should be configured off in t... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.4 Mobility between DECT-2020 Sinks | Since the IPv6 address contains the Sink Long RD ID, whenever an RD moves from under one Sink to another Sink its IPv6 address changes. Mobility under same Sink does not change the IPv6 address. An RD moving under a different Sink shall read the CDD information advertised and follow the operations as defined in CDD [3]... |
8cf81bcf57dac52b3c6db1e734248fb0 | 103 874-3 | 6.5 Border Router or Sink restart | If the downlink routing into the DECT-2020 network is based on selective source routing, any restart or reset of the BR may result in the loss of the routing information. Sink shall be the responsible device to distribute Configuration Data Distribution [3], and in restart situation operate as defined in CDD [3]. An RD... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 1 Scope | The present document describes the PEMEA Audio_Video (PAV) capability, and the need for this functionality. The required entities and actors are identified along with the protocol, specifying message exchanges between entities. The message formats are specified and procedural descriptions of expected behaviours under d... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 2 References | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 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... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 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... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 3 Definition of terms, symbols and abbreviations | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 3.1 Terms | For the purposes of the present document, the following terms apply: security: techniques and methods used to ensure: • authentication of entities accessing resources or data. • authorization of authenticated entities prior to accessing or obtaining resources and/or data. • privacy of user data ensuring access only to ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 3.2 Symbols | Void. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard AESGCM Advanced Encryption Standard key used with GCM AP Application Provider ETSI ETSI TS 103 945 V1.1.1 (2023-11) 11 App Application CN Comfort Noise CPE Cus... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4 PEMEA capability extensions | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.1 Overview of extension in PEMEA | PEMEA extension capabilities are defined in ETSI TS 103 478 [1] and are implemented through the use of "reach-back" URIs. The Application Provider (AP) node advertises capabilities as part of the initial forward message through the network, the Emergency Data Send (EDS) message, and the terminating PSAP Service Provide... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.2 Service support indication and response | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.2.1 Service definition | ETSI TS 103 478 [1] defines the "Audio_Video" typeOfInfo in Table 10, but does not elaborate further on protocols in Table 11. The present document provides a concrete definition of the "Audio_Video" typeOfInfo in PEMEA through the specification of a protocol value. The definition in Table 1 shall be considered as an e... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.2.2 Service support indication | An AP needing to indicate that the Application it is serving can support real-time text using the PEMEA protocol would include the following information element in the apMoreInformation element of the EDS associated with the emergency session: <information typeOfInfo="Audio_Video" protocol="PEMEA"> https://ap.example.p... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.2.3 Service support response | A terminating node that can support the "Audio_Video" "PEMEA" capability includes this capability in the apMoreInformation element returned to the AP in the onCapSupportPost. This is described in clause 11.1.4 of ETSI TS 103 478 [1] with the value for "Audio_Video" "PEMEA" provided in the example below. <apMoreInformat... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 4.2.4 Auto response service | The original intent of many emergency applications was to provide ancillary data to the PSAP that was associated with an emergency voice call that the PSAP had, or soon would, receive. As a consequence, a PIM or tPSP usually notifies the PSAP-CPE when an EDS has arrived, but does not respond to the AP until a PSAP Call... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5 Architecture | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.1 Overview | The PEMEA Audio_Video (PAV) capability is WebRTC-based, so it is necessary to understand a little bit about WebRTC in order to understand what is signalled, to whom and between which entities. This also helps to understand explicitly what is normatively specified in the present document, what is semantic, and what is n... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.2 Architecture and high-level WebRTC flows | WebRTC was designed to use peer-to-peer communications between web browsers, and this means that media stream connections are between peers. In an Audio_Video flow, each participant can have 2 streams to send, one audio stream from a microphone and one video stream from a camera. It is not mandatory to have always both... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.3 Audio_Video logical components | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.3.1 Audio_Video Signalling Server | Audio_Video sessions in PEMEA are established as logical rooms through which participant applications send signalling information. It is the role of the Audio_Video Signalling Server to manage the participants in this room and the transfer of all signalling information associated with the communication between particip... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.3.2 Media Server | The media server in the PAV architecture provides control over media streams as directed through MEDIA_CONTROL messages initiated by the PSAP Call-Taker depending on different circumstances. Examples of where this may be used included supervisory/monitor activities or in emergency circumstances where it is imperative t... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 5.3.3 TURN Server | Modern PSAP deployment isolate the PSAP Call-Taking equipment from inbound services through the use of firewalls. The firewalls control data flow through a symmetric NAT making general connectivity more secure but also more complex than direct communication. The Traversal Using Relays around NAT (TURN) protocol [i.4] w... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 6 Security | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 6.1 Signalling transport security | The PEMEA Audio_Video (PAV) service is identified as an HTTPS URI that resolves to a session signalling room in the PAV server. The connection should be made using TLS 1.3 but may be made using 1.2 and this shall not support fallback below TLS 1.2. The connecting participant shall authenticate to the PEMEA signalling s... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 6.2 Security token usage | The HTTP Authorization header field is defined in IETF RFC 2617 [2] and it specifies that the usage is a scheme followed by a value, where the value may have a structure, as is the case for the digest authentication scheme. Security token usage in the HTTP Authorization header field was originally specified for use wit... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 7 PEMEA Audio_Video codec support | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 7.1 Overview | The PEMEA Audio_Video capability is built around WebRTC, which has an explicitly defined minimum set of codecs that shall be supported by all endpoints. |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 7.2 Audio codec support | WebRTC audio codec support is defined in IETF RFC 7874 [8] and it requires all end-points to support: • Opus as defined in IETF RFC 6716 [9] with the payload defined in IETF RFC 7587 [11]. • Opus codec updates detailed in IETF RFC 8251 [10]. ETSI ETSI TS 103 945 V1.1.1 (2023-11) 17 • G.711, PCMA and PCMU using payload ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 7.3 Video codec support | WebRTC video codec support is defined IETF RFC 7742 [7] and to summarize, it requires all end-points to support: • VP8. • H.264 Constrained Baseline. Recipients of video streams shall be able to decode video at a rate of at least 20 frames per second (fps) at a resolution not less than 320 pixels by 240 pixels. Higher ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8 Initiation procedures | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.1 Overview | This capability requires procedures to be followed by each of the App, AP and PIM nodes during the emergency session establishment. Signalling occurs between the App and AP, and the AP and the associated Audio_Video signalling server as show in Figure 1. Connection management and peer media negotiations occur over the ... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 8.2 App call initiation procedure | The App includes whatever information it normally includes in an initial data exchange with the AP at call time. In addition, it includes support for the PEMEA Audio_Video (PAV) capability. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.