hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 13.5 Cascade-FHM mode | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 13.5.1 General | Following clauses defines one hybrid mode Cascade-FHM. The mode is shown in Figure 13-10. Figure 13-10: Cascade-FHM mode Figure 13-10 shows two typical scenarios in Cascade-FHM mode, one is Same cell scenario, that is O-RU(s) serving cascaded FHMs belong to Same cell, another is Two cells scenario, that is O-RU(s) serv... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 13.5.2 Copy and Combine function | DL Copy function and UL Combine function for Cascade-FHM mode are actually same with FHM mode with a little attention that FHM#1 regards FHM#2 as its one O-RU from aspect of Copy and Combine. Following figures show downlink and uplink flow for Same cell scenario (Figure 13-11) and Two cells scenario (Figure 13-12). ETS... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 13.5.3 Delay management | Delay management for Cascade-FHM mode looks like the combination of FHM mode and Cascade mode while FHM#2 cannot be treated as one normal O-RU from aspect of delay management since it has own processing delay and transport delay towards its O-RUs. Assuming the configuration is two Cascaded FHMs: FHM#1 has one O-RU and ... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 1 Scope | This Technical Specification details the format of a Radio Application Package (RAP). |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 2 References | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 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... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 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... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 3 Definition of terms, symbols and abbreviations | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 3.1 Terms | For the purposes of the present document, the following terms apply: administrative RAP metadata: information to help manage a resource, like resource type, permissions, and when and how it was created descriptive RAP metadata: descriptive information about a resource, such as a target reconfiguration platform, a compi... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 3.2 Symbols | Void. |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BE Back End HAL Hardware Abstraction Layer HW HardWare IR Intermediate Representation MDRC Mobile Device Reconfiguration Class OS Operating System RA Radio Application RAP Radio Application Package RC Radio Controller RE Reconfigurable Equipme... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 4 Usage of Radio Application Packages | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 4.1 Context | A Radio Application Package (RAP) is being used in order to provide new Radio Applications to a target radio equipment. As detailed in ETSI EN 303 648 [i.2] for radio equipment in general and in ETSI EN 303 095 [i.8] for the specific case of mobile devices, the RAP is used for distribution and installation of RA codes ... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 4.2 Reconfiguration Classes | The information to be provided in a Radio Application Package (RAP) is dependent on the level of reprogrammability of the concerned platform. In the present document, it is thus referred to the Mobile Device Reconfiguration Classes (MDRC) as defined in ETSI EN 302 969 [i.7] for reconfigurable Mobile Devices and Radio E... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5 Definition of Radio Application Packages | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.1 Content | In the present clause, the format of the RAP container is described on a high level. In order to keep the approach flexible, each of the information elements will be combined with a length indication (number of octets) such that manufacturers can adapt the size of any information element as required. The high-level RAP... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2 Tree Structure | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.1 Introduction | The RAP is a complex hierarchical bit field which is represented as a graph with specific properties. The RAP bit field is a sequence of bits. Therefore, the graph properties shall insure the only way for the RAP writing operation when the RAP is created as well as the RAP reading operation during which all RAP element... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.2 Top Level | Header URACodeList Security Manufacturer Profile Reserve RAP Figure 5: Top Level Tree Structure The highest layer of the RAP graph consists of the only one the RAP node which represents the whole RAP bit field as it is pointed out in Figure 5 The lower layer consists of the following nodes representing particular RAP s... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.3 Tree - Header Section | Descriptor Structure RadioLib TargetPlatform RAP \Header Reserve ID Version Date Producer ManufacturerFlag InitialProfileFlag RAPReserveFlag HeaderReserveFlag ManufacturerReserveFlag SecurityReserveFlag ReserveFlag Version Date ID ReconfigurationClass (RC) Figure 6: Tree - Header Section The RAP Header subtree is depic... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.4 Tree - Security Section | Profile Integrity Origin Reserve RAP\Security Figure 7: Tree - Security Section The Security section subtree is depicted in Figure 7. Elements of the Security section are described in Table 3. Table 3: Security Section Bit Fields N Node name Node type Bit field 1 Profile mandatory Description of security profile. Indic... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.5 Tree - Unified Radio Application (URA) Code Section | CodeType=source RC=5,6,7 URADescriptor ID URAComponentList Version RAP\URACodeList URACode[1] URACode[2] Date ... Producer URAComponent[1] URAComponent[2] ... Header Code ID CodeType ComponentDescriptor HWComponentID Language OS LibList RVM Name Version Date Name Version Date Lib[1] Lib[2] ... Version Date Link Version... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.6 Tree - Manufacturer Information Section | InstallatorType InstallatorCode Parameters Reserve RAP\Manufacturer Figure 9: Tree - Manufacturer Information Section The Manufacturer Information section subtree is depicted in Figure 9. Elements of the Manufacturer Information section are described in Table 5. Table 5: Manufacturer Information Section Bit Fields N No... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.2.7 Tree - Initial Profile Section | URA[1]InitialProfile URA[2]InitialProfile ... RAP\InitialProfileURAList Figure 10: Tree - Initial Profile Section The Initial Profile section subtree is depicted in Figure 10. It represents a list of Initial Profiles for each URA from the RAP. Each URA Initial Profile is a bit field which internal structure is recogniz... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3 Internal Structure | |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3.1 Introduction and conventions | Within the RAP Top Level Tree structure introduced in clause 5.2.1, the structures of the various information fields are further detailed in the present clause. The definition of the information elements follows in clause 5.2.2 to 5.2.7. NOTE: In the graphical representations in this clause, the structures of the packa... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3.2 Radio Application Package (RAP) Header | The Radio Application Package Header consists of a sequence of static fields which size is defined in Table 6, clause 5.4. The format the sequence is presented in Figure 13 and the structure is described by the graph in Figure 12. Only the Reserve field is the dynamic field. It is optional field and it takes in place w... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3.3 Security Section | Following a risk analysis, ETSI TS 103 436 [1] introduces security requirements for reconfigurable radio systems. The Security Section includes the following information elements: i) a Security Profile (d) which details the structure of the security section and includes security information available in the reserve par... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3.4 Unified Radio Application (URA) Code Section | The Unified Radio Application Package Code Section consists of the list of particular URA subsection which format is depicted in Figure 14 and the structure is explained in clause 5.2.2. Each URA[k] subsection, for some k = 0, 1,…, consists of the static field URA Descriptor and the list of URA components. The URA Desc... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.3.6 Initial Profile Section | The Initial Profile Section is the optional field which take place when InitialProfileFlag = 1. It represents the list of initial profiles of particular URAs: URA[k] Initial Profile, for k = 1, 2,… . Each URA[k] Initial Profile, for some k, is the dynamic field which structure and size are defined by a particular manuf... |
31cd933f5d13416193ceb3a5b77047f4 | 103 850 | 5.4 Format | The present clause introduces the detailed information contained in the high level Radio Application Packet structure as defined above. Table 6 summarizes information about bit fields of the RAP. The column "Path\Node Name" navigates the way from the root node which is "RAP" to the target node with corresponding "Node ... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 1 Scope | The present document defines the Test Purpose for IPv6-only services over 5G, covers roaming and non-roaming test scenarios. |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 2 References | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 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... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 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... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 3 Definition of terms, symbols and abbreviations | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 123 501 [1], IETF RFC 6146 [i.2], IETF RFC 6147 [i.3], IETF RFC 6877 [3], IETF RFC 7050 [i.4], IETF RFC 7915 [i.5] and the following apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [i.1]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 3.2 Symbols | Void. |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project 5GC 5G Core 5GC_A 5G Core for A network 5GC_B 5G Core for B network AC4 ACcess of Internet IPv4 servers AC6 ACcess of Internet IPv6 servers AMF Access and Mobility Function ATM Abstract Test Method ATS A... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 4 Test Configurations | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 4.1 General | Test purposes of the present document address the 5GS and IPv6-only functional entities. CLAT is at the UE, sharing an interface with UE. DNS64 and NAT64 are accessible via N6. N6a represents the interface between NAT64 and DN to observe translation behaviours. |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 4.2 Test configuration | Figure 1: Test configuration CF_5G_IPv6only_NRMI Configuration CF_5G_IPv6only_NRMI is used for a network where users are registered to their home network. The suffix NRMI stands for non-roaming scenario. PDU session establishment procedures of UEs are performed locally in their own home network. Configuration CF_5G_IPv... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 5 Test Suite Structure (TSS) | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 5.1 Structure for IPv6 only services over 5G test purposes | Table 2 shows the Test Suite Structure (TSS) including its subgroups defined for interoperability testing of test purposes of IPv6 only services over 5G. • UE IPv6 address allocation in 5G core network • DNS64 address allocation • NAT64 prefix discovery • Access of Internet IPv4 servers • Access of Internet IPv6 server... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6 Test Purposes (TP) | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.1 General | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.1.1 Test strategy | The test purposes were generated as a result of analysis of the base documents [1], [2], [3]. |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.1.2 TP naming convention | TPs are numbered, starting at 01, within each group. Groups are organized according to the TSS. Table 3: TP identifier naming convention scheme Identifier: <TP>_<group>_<scope>_<nn> <TP> = Test Purpose: fixed to "TP" <group> = test group: RMIL Roaming with local breakout RMH Roaming with home routed NRMI Non-roaming <s... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.1.3 TP structure | Each TP has been written in TDL-TO and thus in a structured manner which is consistent with all other TPs. The intention of this is to make the TPs more formal. In addition, a more readable format is provided by generating tables out of the TDL-TO format. The defined structure, that has been used, is illustrated in tab... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.2 Test Purposes | |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.2.1 Test Purposes in the non-roaming scenario | TP Id TP_NMRI_IPAA_01 Test Objective Verify that the 5GC provides the IPv6 prefixes to the UE Reference NONE Configuration CF_5G_IPv6only_NMRI PICS Selection NONE Initial Conditions with { the 5GC has a UE registered to it which is provisioned with the IPv6 only DNN and the 5GC is provisioned with selectable DNN config... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.2.2 Test Purposes in the roaming with local breakout scenario | TP Id TP_RMIL_IPAA_01 Test Objective Verify that the 5GC_A provides the IPv6 prefixes to the UE Reference NONE Configuration CF_5G_IPv6only_RMIL PICS Selection NONE Initial Conditions with { the 5GC_A has a UE registered to it which is provisioned with the IPv6 only DNN and the 5GC_A is provisioned with selectable DNN ... |
a9f9332e308931eb0ab38a91361614ef | 103 878-1 | 6.2.3 Test Purposes in the roaming with home routed scenario | TP Id TP_RMIH_IPAA_01 Test Objective Verify that the 5GC_B provides the IPv6 prefixes to the UE Reference NONE Configuration CF_5G_IPv6only_RMIH PICS Selection NONE Initial Conditions with { the 5GC_A has a UE registered to it which is provisioned with the IPv6 only DNN and the 5GC_B is provisioned with selectable DNN ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 1 Scope | The present document describes a Native IP end-to-end broadcast system based on existing DVB standards. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 2 References | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 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... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 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... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 3 Definition of terms, symbols and abbreviations | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 3.1 Terms | For the purposes of the present document, the following terms apply: aggregator: any entity in charge of aggregating one or more bouquets of services asset: any file object directly retrievable by NIP Clients through a URI bootstrap process: initialization process for broadcast receivers joining a NIP broadcast network... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 3.2 Symbols | Void. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABR Adaptive Bit Rate ALC Asynchronous Layered Coding API Application Programming Interface AV Audio Visual ETSI ETSI TS 103 876 V1.1.1 (2024-09) 15 AVC Advanced Video Coding B2B Business to Business B2C Business to Consumer CA Conditional Acc... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 4 System Description | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 4.1 Overview | The present document describes a Native IP (NIP) Broadcast System based on existing DVB technologies that have been adapted and complemented for the requirements of network operators and broadcasters that want to leverage IP for the distribution of content. It is designed to be applicable to DVB-S2X, DVB-S2 and DVB-T2 ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 4.2 System Features | The DVB Native IP Broadcast System works in both connected and unconnected scenarios. In unconnected scenarios, i.e. without return path, some features are not available yet. The core features of the Native IP solution are: 1. Carriage of real-time live linear television and radio services: - Real-time delivery of asse... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5 Overall System Architecture | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.1 Introduction | The DVB Native IP (DVB-NIP) specification describes an end-to-end IP delivery architecture leveraging Internet content delivery technologies such as Adaptive Bit Rate (ABR) streaming also for broadcast applications. The DVB-NIP Broadcast System is made up of two major parts (see figure 5.3-1): • All functions related t... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.2 Layered System Design | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.2.1 General | The DVB-NIP Broadcast System relies on a layered system architecture. At the top of the Native IP stack is a DVB-I based television service discovery and metadata layer according to ETSI TS 103 770 [9]. This layer is responsible for informing receivers about the various services available on the broadcast and broadband... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.2.2 Core DVB Specifications underlying NIP (informative) | The DVB-NIP Broadcast System is based on the following core DVB specifications. This list is purely informative and the exhaustive list is provided in clause 2. • DVB-I (ETSI TS 103 770 [9]) provides the service discovery and programme metadata scheme for the DVB-NIP Broadcast System. DVB-NIP is designed in such a mann... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.3 End-to-End System Architecture | The DVB-NIP Broadcast System is significantly different from traditional Transport Stream based broadcast architectures. Content sourcing in a NIP context is no longer from a dedicated DVB Encoding Platform but from the same Content Preparation and Hosting Platform that also source(s) OTT platforms. The OTT headend fun... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.4 NIP Headend Functions (informative) | The DVB-NIP Headend is made up of the following high-level functions (each with nested sub-functions): 1. The OTT Content Preparation and Hosting platform consists of media encoding, Content Encryption, Content Packaging and Content Hosting functions. It generally provides the same streams for over-the-top content deli... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 5.5 NIP Reference Points | The following is a listing of logical reference points specific to the DVB-NIP Broadcast System as specified in the present document (see figure 5.3-1): NH1: The interface between the Native IP Service Aggregation platform and the Native IP Signalling Server. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 22 NH2: The interface ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6 Receiver Deployment Models (informative) | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.1 Introduction | The present specification targets three receiver Deployment Models (DMs) in particular. This listing is not exhaustive, and industry can come up with other Deployments Models, but this particular logical grouping should help implementations of Native IP receivers. Other deployment models not described here may be added... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.2 Generic Receiver Design | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.2.1 Introduction | This clause describes the generic virtual functions that are part of NIP Receivers. Not all receivers need to implement all functions. Receiver functions are there to describe and structure the receiver design. Some functions may be combined, or some functions may not exist at all in some receiver implementations. Clau... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.2.2 NIP Gateway Functions | All NIP Gateways include the following sub-functions: • Single or multiple DVB-S2/S2X/T2 tuner(s)/demodulator(s). • The capability to receive at least one of the two: MPE via TS or GSE-Lite via GSE-HEM. • The capability to receive IP multicast streams (with and without IP Robust Header Compression applied). • The capab... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.2.3 NIP Client Functions | The NIP Client includes the following sub-functions: • The capability to interact with a DVB-I Service List Entry Points Registry Server. • The capability to interact with a DVB-I Service List Server. • The capability to display a DVB-I Service List to the End User. • The capability to select the most appropriate insta... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.3 Professional Edge Cache Receiver (DM1) | Professional Edge Cache Receivers according to the present document are deployed at the edge of telecom, CDN or broadcast networks or act as local wireless hotspots. They receive DVB-NIP formatted content from a broadcast network via multicast and make that content available locally to other networks (e.g. CDN, Fixed, ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.4 Integrated Native IP TV (DM2) | The same DVB-NIP broadcast streams that are built for feeding professional DM1 receivers can also be used for direct reception at home. The simplest reception solution for consumer applications under the present document is DM2. It refers to a fully integrated smart television set. Television sets according to DM2 migh... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.5 Home Gateway + IP Client (DM3) | Deployment Model 3 (DM3) is a split model in which the NIP Gateway and the NIP Client functions are implemented in separate devices. The NIP Gateway may be an additional feature of an existing hardware device such as a TV set, a STB, an antenna multiswitch, etc. or may be a dedicated standalone Gateway device located o... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 6.6 Receiver Configurations and Deployment Models | Depending on the specific deployment model, receiver configurations may require different functions and features to be implemented. Table 6.6-1 associates the receiver functions and the deployment models. At least "Mandatory" subsystems and functionalities need to be implemented in reception equipment to comply with th... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7 Native IP Carriage | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.1 Introduction | DVB Native IP is designed for deployment on top of the following physical layer systems: • DVB-S2X (ETSI EN 302 307-2 [2], ETSI EN 302 307-1 [1]); • DVB-S2 (ETSI EN 302 307-1 [1]); and • DVB-T2 (ETSI TS 102 755 [3]). The data link layer in DVB Native IP uses either: • Generic Stream Encapsulation (GSE), ETSI TS 102 606... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.2 Physical Layer: DVB-S2X, DVB-S2, DVB-T2 | 7.2.1 Overview There is a high degree of commonality between DVB-S2X (ETSI EN 302 307-2 [2]), DVB-S2 (ETSI EN 302 307-1 [1]) and DVB-T2 (ETSI TS 102 755 [3]) with regards to the mode adaptation, but some settings for NIP purposes are specific to each physical layer system and hence related definitions are described sep... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.2.2 DVB-S2X | The entirety of DVB-S2X is defined by the two specifications ETSI EN 302 307-1 (DVB-S2, [1]) making up the core part and (ETSI EN 302 307-2 [2]) (DVB-S2X) making up the extension of and the difference to the core part. The whole physical layer system DVB-S2X can be deployed as defined by the two aforementioned specific... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.2.3 DVB-S2 | DVB-S2 is defined by the specification ETSI EN 302 307-1 [1]. The whole physical layer system DVB-S2 can be deployed as defined by the aforementioned specification - with the following attributes and restrictions: System configurations (table 1, clause 4.3 of ETSI EN 302 307-1 [1]): • "Broadcast Services" is used for c... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.2.4 DVB-T2 | DVB-T2 is defined by ETSI TS 102 755 [3]. The whole physical layer system DVB-T2 can be deployed as defined by the aforementioned specifications - with the following attributes and restrictions: System overview (clause 4.1 of ETSI TS 102 755 [3]): • It is assumed that the receiver will always be able to decode one data... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.3 Data link layer: GSE-Lite, MPE | 7.3.1 Overview Depending on the physical layer system deployed, either GSE (ETSI TS 102 606-1 [4], ETSI TS 102 606-2 [5], ETSI TS 102 606-3 [6]) with its GSE-Lite profile or MPE (ETSI EN 301 192 [7], clause 7) is used on the data link layer. Further details are outlined in clauses 7.3.2 and 7.3.3. 7.3.2 Generic Stream ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4 Network Layer: IP RObust Header Compression (ROHC) | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.1 Introduction and Principles | DVB-NIP provides support for both uncompressed and compressed IP header transport. When IP header compression is used, the IP header compression scheme shall be ROHC-U as described in GSE-ROHC, ETSI TS 102 606-3 [6]. In the GSE-ROHC framework, multiple header compression profiles are defined. Each profile indicates a s... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.2 ROHC channel mapping | The ROHC framework defines channels to identify the compressed packet flows. In a DVB-NIP system, a single ROHC channel shall be configured per GSE stream. Therefore, the Link ID can be mapped to a ROHC channel ID and the CID is managed separately for each GSE stream. |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.3 Context ID (CID) assignment | The CID can be assigned for each IP stream based on the combinations of upper layer protocols. An IP stream can be classified based on the IP address and port number. It can be considered as the same IP stream when the IP packet has the same combination of source IP address, destination IP address, source UDP port, and... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.4 Transmission of Context Information | In the case of unidirectional links, if a receiver has no context information, the ROHC decompressor cannot recover the received packet header until it receives full context data. The context information and configuration parameters are sent in the ROHC-U descriptor or ROHC-U multicast descriptor. Based on the GSE-ROHC... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.5 Link Layer Signalling | Generally, link layer signalling operates below the IP layer. In the receiver, link layer signalling can be obtained earlier than IP-level signalling such as announcement channel signalling. ETSI ETSI TS 103 876 V1.1.1 (2024-09) 33 Figure 7.4.5-1 shows the data link layer architecture and related identifiers on the tra... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.6 Descriptors for the NIP system | To support the GSE layer structure above and multicast delivery, the following descriptors can be used for link layer signalling in an NIP system. • IP Multicast List descriptor: This descriptor conveys a list of IPv4 multicasts carried in a physical link. This descriptor also provides additional information for proces... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.4.7 Link Layer Signalling Example (informative) | Figure 7.4.7-1 shows the construction of link layer signalling using GSE-LLC. Figure 7.4.7-1: Mapping to LLC tables and lookup path for DVB-NIP Multiple logical IP multicast configuration loops can be considered in a NCD record table. Each IP multicast configuration loop contains a target loop and an operational loop. ... |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.5 Transport Layer: DVB-MABR | |
3ed9b1d5a5636f2a4248b07cbcad7b9b | 103 876 | 7.5.1 DVB-MABR Scope | NIP according to the present document relies on DVB-MABR for the transport of Media Objects. Every NIP Stream shall have a single Multicast Server function according to ETSI TS 103 769 [8] associated with it, generating all the multicast transport objects for that NIP stream. A single logical Multicast Server function ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.