hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.2 Shared O-RU Management during O-DU SW Update | The context of the Shared O-RU Management during O-DU SW Update is captured in table 4.20.3.15.2-1. Table 4.20.3.15.2-1: Shared O-RU Management during O-DU SW Update Use Case Stage Evolution / Specification <<Uses>> Related use Goal Shared O-RU Management during O-DU SW update. Actors and Roles • SMO: Facilitates the e... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.3 Shared O-RU Management during O-DU SW Update Monitoring and Mitigation | The context of the Shared O-RU Management during O-DU SW Update Monitoring and Mitigation is captured in table 4.20.3.15.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 140 Table 4.20.3.15.3-1: Shared O-RU Management during O-DU SW Update Monitoring and Mitigation Use Case Stage Evolution / Specification <<Uses>> Related u... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4 Required data | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.1 Required data for all Shared O-RU Use Cases | The following required data is relevant to the following sub-use cases: Resource partitioning, Start-up, Configuration, Supervision, Performance Management, ALD control, Antenna Calibration, Rehoming, and Shutdown: • Inventory system maintains inventory data for the Shared O-RUs because it needs to be able to identify ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.2 Required data for single MNO Configurations | The following data applies for single operator configurations when used by the other Shared O-RU sub-use cases: • Non-RT RIC needs to be able to partition the Shared O-RU carriers between O-DU nodes operated by the same MNO. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.3 Required data for multi-MNO Configurations | The following data applies for multi-operator configurations when used by the other Shared O-RU sub-use cases: • The resource partitioning rApp needs to be able to partition the Shared O-RU carrier resources between different O-DU nodes of different MNOs. • Shared O-RU needs to be able to associate management accounts ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.4 Required data for Resiliency Use Cases | The following data is used by the resiliency use case: • The supervision needs to include the O-DU identity because the Shared O-RU needs to be able to support supervision on a per O-DU basis. • Alarm data needs to be kept at the Shared O-RU because the Shared O-RU needs to be able to terminate transmissions associated... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21 Use case 21: Energy Saving | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.0 Introduction | This section provides the motivations, descriptions, and proposed solutions for different Energy Efficiency and Energy Saving features (sub-use cases). While there are energy savings by improving base station hardware efficiency and by the evolution of radio access technologies, the EE/ES use case primarily addresses e... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.1 Background and goal of the use case | The RAN is responsible for a major part of the Energy Consumption (EC) of a mobile network, and the O-RU accounts for the largest part of the energy consumption of the RAN. The rarefication of fossil fuel-based energy resources and the urgent need to reduce CO2 emissions make the EC a strategic topic for network operat... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.2 Entities/resources involved in the use case | Editor's note: If possible, single common description for all sub-use cases. Deployment option 1: AI/ML inference host located in the Non-RT RIC 1) Non-RT RIC: a) Collect configurations, performance indicators and measurement reports (e.g. cell load related information and traffic information, EE/EC measurement reports... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3.0 Introduction | Editor's note: Sub-use case specific solutions with detailed descriptions in fully separate sections. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3.1 Carrier and Cell switch off/on | Mobile networks often utilize multiple frequency layers (carriers) to cover the same service area. At low load, ES can be achieved by switching off one or more carriers or entire cells without impairing the network performance. The switch off/on decision can be made by an AI/ML model within the inference host, deployed... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.4 Required data | Input Data 1) E2 Node to SMO and Near-RT RIC (when Near-RT RIC serves as inference host): ETSI ETSI TS 104 036 V12.0.0 (2025-04) 150 • EE/EC measurement reports. • Load statistics per cell and per carrier, such as number of active users, average number of RRC connections, average number of scheduled active users per TT... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22 Use case 22: MU-MIMO Optimizaiton | This use case provides the motivation, description, and requirements for a near real time MU-MIMO optimization control loop deployment. Deploying MU-MIMO application in the Near-RT RIC enables new solutions that can optimize UE and cell level performance in certain deployments by e.g. deriving channel estimation/predic... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.1 Background and goal of the use case | MU-MIMO is one of the key technologies available for increasing UE and cell capacities using existing time/frequency resources. The use of multiple antennas enables the pointing of beams to multiple UEs with each beam spatially filtering the interference from the other beams. This has the potential to provide higher to... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.2 Entities/resources involved in the use case | 1) Near-RT RIC: a) Retrieve cell configuration and UE states from E2 nodes. b) Send configurations for DL channel estimation reporting and UL SRS and DMRS to the E2 nodes. c) Retrieve DL/UL traffic, and DL/UL channel quality information from E2 nodes. d) Use the retrieved information to select the UEs to be spatially m... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.3.1 MU-MIMO Optimization | The context of MU-MIMO Optimization is captured in table 4.22.3.1-1. Table 4.22.3.1-1: MU-MIMO Optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal MU-MIMO optimization using Near-RT RIC control loop. Actors and Roles Near-RT RIC: configures E2 nodes' measurements, collects data from E2 Nodes... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.4 Required data | The Near-RT RIC requires different types of data from the E2 Nodes as summarized below with examples: 1) Cell configuration information (e.g. frequency and BW, FDD/TDD, SCS, UL-DL configuration) 2) List of connected UEs 3) UE connection updates (setup, release, handover) 4) UE RRC state changes (connected, inactive, id... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.23 Use case 23: Sharing Non-RT RIC Data with the Core | Void. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 153 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24 Use case 24: Industrial vision SLA Assurance | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support industrial vision Service Level Agreement (SLA) Assurance. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.1 Background and goal of the use case | Industrial vision is an image recognition technology used for work piece inspecting, processing and assembling automation, as well as the monitoring and controlling of production process by replacing human eyes with cameras for various measurements and judgments. The main feature of industrial vision system is that it ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Support communication of non-RAN data to enrich control functions in Near-RT RIC (enrichment information). 2) Near-RT RIC: a) Support communication of pre-scheduling configuration parameters to E2 Node. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 154 3) E2 Node: a) Support pre-scheduling parameters configu... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.3 Solutions | The context of Industrial vision assurance is captured in table 4.24.3-1. Table 4.24.3-1: Industrial vision assurance Use Case Stage Evolution / Specification <<Uses>> Related use Goal Meeting industrial vision service SLA requirement via dynamic pre-scheduling parameter configuration. Actors and Roles Non-RT RIC, Near... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.4 Required data | Enrichment Information are expected to be retrieved by Non-RT RIC for industrial vision SLA assurance. Service data transmission information from E2 Node are also expected to be collected by Near-RT RIC for industrial vision assurance. 1) Enrichment information: a) Production-line and industrial vision camera configura... |
98d566ac142ee06783f646c81587b072 | 104 025 | 1 Scope | The present document defines the interfaces through which a DVB-HB Local Server can redistribute broadcast signals and associated metadata to DVB-HB Clients and specifies mechanisms allowing a DVB-HB Local Server to announce its presence on the LAN and its capabilities, and a DVB-HB Client to discover it. It includes b... |
98d566ac142ee06783f646c81587b072 | 104 025 | 2 References | |
98d566ac142ee06783f646c81587b072 | 104 025 | 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... |
98d566ac142ee06783f646c81587b072 | 104 025 | 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... |
98d566ac142ee06783f646c81587b072 | 104 025 | 3 Definition of terms, symbols and abbreviations | |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.1 Terms | For the purposes of the present document, the following terms apply: DVB Gateway: device which may provide functions of a DVB-HB Local Server, a DVB-NIP Gateway or both ETSI ETSI TS 104 025 V1.1.1 (2024-07) 12 DVB-HB Client: unit capable of connecting to a DVB-HB Local Server and processing and/or rendering content NOT... |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.2 Symbols | Void. |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACFEC Adaptive Cross-layer Forward Error Correction AIT Application Information Table AL-FEC Application Layer - Forward Error Correction AP Access Point API Application Programming Interface APP APPlication-specific ARP Address Resolution Pro... |
98d566ac142ee06783f646c81587b072 | 104 025 | 4 Concepts and overview | The DVB Home Broadcast (DVB-HB) concept enables client devices to access and consume broadcast content that has been retransmitted, through Internet Protocol (IP) means, by a local server located in the same IP subnetwork such as a Local Area Network (LAN). Client devices, including those which cannot access linear bro... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5 DVB-HB Reference architecture | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.1 Introduction | The relationships between the logical functions in the reference architecture are identified by named reference points. In a practical deployment, each of these is realized by a concrete interface and conveys information between the relevant functions using a specific protocol. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.2 Reference architecture diagram | Figure 1 summarizes the simplified DVB-HB reference architecture, showing the reference points and the logical functions. Data plane interactions are depicted using solid lines. Control plane interactions are depicted using dotted lines. Interactions that lie within the scope of the present document are depicted as bla... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3 Reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1 Data plane reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.1 Introduction | The reference points defined in this clause are used primarily to transport content and service list metadata. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.2 Generic data plane reference points (Profiles A and B) | I Input RF interface between Digital Video Broadcasting (DVB) broadcast networks and the Tuners function of a DVB-HB Local Server. Input signals can be any of the following: • DVB Satellite Framing and Modulation (DVB-S) signals as defined in ETSI EN 300 421 [4]. • DVB Satellite Framing and Modulation, Second Generatio... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.3 Specific data plane reference points for Profile A | I See clause 5.3.1.2. L_A Delivery of content via Real Time Streaming Protocol (RTSP)/Real Time Protocol (RTP) or HTTP interaction between the Content publication function of a Profile A DVB-HB Local Server and the Content Playback function of a Profile A DVB-HB Client, according to EN 50585 [1], and additional optiona... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.4 Specific data plane reference points for Profile B | I See clause 5.3.1.2. L_B HTTP(S) interaction between the Origin server subfunction of a Profile B DVB-HB Local Server and the DVB-DASH client subfunctions of a Profile B DVB-HB Client for content delivery, and eventually the Data file extraction subfunction in case of additional data files (e.g. an interactive applica... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2 Control plane reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.1 Introduction | The reference points defined in this clause are used for control signalling. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.2 Generic control plane reference points (Profiles A and B) | CL Control interface for request of a specific service by a DVB-HB Client. CA Control interface for discovery and capability exposure of DVB-HB Local Servers. CS Control interface for forwarding service requests to the Service Request Handler) function (out of scope of the present document). CT Control interface for co... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.3 Specific control plane reference points for Profile A | CL_A Control interface for request of a specific service by a Profile A DVB-HB Client, based on RTSP or HTTP requests according to EN 50585 [1]. NOTE: CL_A and L_A reference points physically correspond to requests and responses of the RTSP or HTTP communication between Streaming Server (SAT>IP) and SAT>IP client subfu... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.4 Specific control plane reference points for Profile B | CL_B Control interface for request of a specific service by a Profile B DVB-HB Client, based on HTTP(S) requests of MPD files according to ETSI TS 103 285 [2]. NOTE: The CL_B reference point corresponds to interface D1 defined in ETSI TS 103 770 [3]. CA_B Control interface for discovery and exposure of capabilities of ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4 Functions | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.1 DVB broadcast networks | This is an external function, out of scope of the present document. It represents deployed on-the-air DVB satellite and/or terrestrial and/or cable broadcast networks, delivering audio/video services to consumer devices (e.g. TVs/Set Top Box (STB)s). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 21 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.2 Tuners | Hardware modules receiving and demodulating on-the-air DVB-S/DVB-S2/DVB-S2X/DVB-T/DVB-T2/DVB-C/DVB- C2 signals, providing in output the relevant TS. Multiple modules may be available, each of them producing a TS. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3 Service List publication | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.1 General description | The Service List publication function generates and maintains the Service List and the associated Content Guide describing the services offered by a DVB-HB Local Server, and publishes it on the LAN for DVB-HB Clients requesting it. The function includes a Service List compilation subfunction generating Service List(s) ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.2 Service List publication for Profile A | In case of Profile A, Service List publication is an optional function, i.e. DVB-HB Clients can use other means for service discovery, e.g. frequency scan via remote tuning commands. The Service List compilation subfunction should generate service lists according to M3U format and/or according to XML format as defined ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.3 Service List publication for Profile B | In case of Profile B, the Service List compilation subfunction generates Service List(s) and associated Content Guide according to the XML formats as defined in ETSI TS 103 770 [3]. Eventually, it may also generate additional signalling files, e.g. an XML-encoded Application Information Table (AIT) associated to an int... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4 Content preparation | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.1 General description | The Content preparation function has the task of producing the selected audio/video content for publication on the LAN, on the basis of the TS demodulated by the Tuners function. It includes a PID selection/processing subfunction, with the task of selecting the Packet IDentifier (PID)s associated with the desired servi... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.2 Content preparation for Profile A | In case of Profile A, in addition to the PID selection/processing subfunction described in clause 5.4.4.1, a TS/IP encapsulation subfunction has the task of encapsulating TS packets in RTP packets carried in User Datagram Protocol (UDP) packets carried in IP datagrams (i.e. TS/RTP/UDP/IP) as defined in EN 50585 [1]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.3 Content preparation for Profile B | In case of Profile B, in addition to the PID selection/processing subfunction described in clause 5.4.4.1, the following subfunctions exist: • Content decoding subfunction, with the task of decoding the A/V content (and associated data) of the selected service. • Content encoding subfunction, with the task of transform... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5 Content publication | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.1 General description | The Content publication function has the following tasks: • Listening to requests from DVB-HB Clients over the CL reference point and triggering tuning commands by forwarding such requests in a proper format to the Service request handler function over the CS reference point. • Making the content available for delivery... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.2 Content publication for Profile A | In case of Profile A, the Streaming server (SAT>IP) subfunction interacts with the Content playback function by receiving requests over the CL_A reference point, triggering tuning commands and delivering the requested content over the L_A reference point according to the protocols defined in EN 50585 [1]. ETSI ETSI TS ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.3 Content publication for Profile B | In case of Profile B, the Content Publication function consists of an Origin Server subfunction (HTTP(S) server), which interacts with the Content playback function by receiving requests over the CL_B reference point, triggering tuning commands and delivering the requested content over the L_B reference point according... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.6 Service request handler | The Service request handler function has the task of converting DVB-HB Client requests, as intercepted by the Content publication function and forwarded over the CS reference point, to tuning commands sent to the Tuners function over the CT reference point. It consists of a Resource allocation subfunction, responsible ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.7 DVB-HB Local Server announcement | The DVB-HB Local Server announcement function has the task of providing advertisements of the presence of a DVB-HB Local Server on the LAN and providing description of the DVB-HB Local Server capabilities (e.g. number and type of tuners, etc.). |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.8 DVB-HB Local Server discovery | The DVB-HB Local Server discovery function is a function of a DVB-HB Client with the task of searching on the LAN for available DVB-HB Local Servers and retrieving their capabilities. See also clause 6 for protocols used. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.9 Service discovery and selection | The Service discovery and selection function is an application of a DVB-HB Client with the task of compiling a local copy of the Service List, collecting Content Guide metadata and controlling the Content playback function. In case of Profile A, Service List(s) and Content Guide data may be retrieved over the M referen... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.10 Resource availability map function | The Resource availability map function is an optional function with the task of exposing the static capabilities of the device (e.g. number and type of tuners) and the instantaneous resources availability in order to efficiently allow sharing the resources among multiple DVB-HB Clients. The function includes a Device c... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11 Content playback | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.1 General description | The Content playback function is the entity in the DVB-HB Client managing request, reception and presentation of content. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.2 Content playback function for Profile A | In case of Profile A, request and reception of the selected service are managed by the SAT>IP client subfunction. It interacts with the Content publication function of the DVB-HB Local Server by sending requests over the CL_A reference point and retrieving the requested content over the L_A reference point according to... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.11.3 Content playback function for Profile B | In case of Profile B, request and reception of the selected service are managed by the DVB-DASH client subfunction. It sends HTTP(S) requests to the Origin server subfunction of the DVB-HB Local Server over the CL_B reference point, retrieving the requested content over the L_B reference point as defined in ETSI TS 103... |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.12 External repository | This is an external function, out of scope of the present document. It represents an external repository (e.g. a remote server, a Universal Serial Bus (USB) memory stick, etc.) of service list metadata, accessed by the Service List publication function via the proprietary reference point E in alternative to generating ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6 DVB-HB Local Server announcement and discovery | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.1 Introduction | In Profile A, in order to ensure backwards compatibility with existing devices supporting EN 50585 [1], the DVB-HB Local Server Announcement and DVB-HB Local Server discovery functions are implemented using a simplified version of Universal Plug and Play (UPnP) according to ISO/IEC 29341-1-1 [13]. In Profile B, the mai... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.2 Profile A DVB-HB Local Server discovery | Profile A DVB-HB Local Server announcement and discovery shall be implemented according to EN 50585 [1]. The mechanism relies on the Simple Service Description Protocol (SSDP) as specified in ISO/IEC 29341-1-1 [13]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3 Profile B DVB-HB Local Server discovery | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.1 Introduction | Profile B DVB-HB Local Server announcement and discovery shall be implemented according to mDNS and DNS-SD, as described in clause 6.3.5. Additionally, a Profile B DVB-HB Local Server may implement one or more of the discovery mechanisms described in clause 6.3.2, clause 6.3.3 and clause 6.3.4. Different implementation... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.2 Optional discovery mechanism based on UPnP | When targeting clients capable of UPnP-based discovery, a Profile B DVB-HB Local Server implementing this method shall announce its presence on the LAN according to EN 50585 [1], with the differences indicated below. The mechanism relies on the SSDP as specified in ISO/IEC 29341-1-1 [13]. With respect to EN 50585 [1], ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.3 Optional discovery mechanism based on HTTP | When targeting clients capable of port-scanning a selected subnet, a Profile B DVB-HB Local Server implementing this method shall announce its presence on the LAN by exposing its Service List Entry Points on Transmission Control Protocol (TCP) port 61 277 (HTTP). During the discovery phase, DVB-HB Clients may scan the ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.4 Additional implementation-specific mechanisms | In addition to the optional discovery mechanisms specified above, other implementation-specific mechanisms supporting browser-based clients may be used. In this informative clause, two specific mechanisms are considered since they are closely related to similar solutions adopted in the present document or in other DVB ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5 Discovery mechanism based on mDNS/DNS-SD | |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.1 General | The method described in the present clause is intended to be applicable in DVB-HB and DVB-NIP [i.1] contexts. In particular, the term DVB Gateway indicates a device which may provide functions of a DVB-HB Local Server as defined in the present document, a DVB-NIP Gateway as defined in DVB Document A180 [i.1], or both. ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.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... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.3 Service Record (SRV) | The SRV record has the following structure, as defined in IETF RFC 6763 [14] and IETF RFC 2782 [16]: <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... |
98d566ac142ee06783f646c81587b072 | 104 025 | 6.3.5.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... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7 Exposure of DVB-HB Local Server capabilities | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.1 Introduction | This clause defines how Profile A and Profile B DVB-HB Local Servers can announce their capabilities to DVB-HB Clients, including number and type of available tuners and encoding resources, together with any restrictions because of concurrent usage by other connected DVB-HB Clients. Clause 7.2 and clause 7.3 provide th... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.2 Device capabilities | Capabilities of a DVB-HB Local Server are defined according to pseudocode 3, table 2 and table 3. HBLocalServerType replicates the same structure as defined by EN 50585 [1], aligned to UPnP syntax according to ISO/IEC 29341-1-1 [13], also for Profile B DVB-HB Local Servers. HBServiceAvailabilityType is used by both Pro... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3 Service Availability Map | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.1 Introduction | The effective availability of a service for a DVB-HB Client can be impacted by several limitations, including: • Unavailability of a frontend (tuner). • Unavailability of a sub-band, or polarization and sub-band, in case of Direct To Home (DTH) reception. • Processing limitations of a DVB-HB Local Server. • Bandwidth l... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.2 Logical structure of the Service Availability Map | The comprehensive logical structure is organized in form of an XML document describing the dependencies among resource usage associated to each service. This is described in the file ServiceAvailabilityMap.xml, which is referred to in the device capabilities exposed by the DVB-HB Local Server (see clause 7.2). Logical ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.3 ServiceAvailabilityMap.xml document | The ServiceAvailabilityMap.xml document is structured in a hierarchy of <DependencyResourceGroup> elements. All child <DependencyResourceGroup> elements are dependent to each other, i.e. if one of these child elements is in use by a DVB-HB Client, it limits usage of other child elements belonging to the same parent <De... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4 Management and processing of the Service Availability Map | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.1 Building the Service Availability Map | The hierarchy of the <ServiceAvailabilityMap> element is intended to describe the mutual dependency of several services' usage, whether transcoded or not. Apart from transcoding or limitation on maximum number of clients, only resources which have a mutual impact on each other's usage need to be grouped in the same <De... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.2 Aligning the Service Availability Map with DVB-I Service List updates | A DVB-HB Local Server implementing this feature shall update the <Service> elements in the ServiceAvailabilityMap.xml document to keep it aligned with the DVB-I Service List. Each time the DVB-I Service List is updated and the @version attribute has a new value, the DVB-HB Local Server shall also update the ServiceAvai... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.3 Updating the Service Availability Map when assigning a service to a client | A DVB-HB Local Server implementing this feature shall update the usage attributes (i.e. @used, @transcodedUsed, @totalServedClients, @totalTranscodedClients) in the ServiceAvailabilityMap.xml document each time a stream representing a service is delivered to a DVB-HB Client, according to the procedure shown in pseudoco... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.