The Obeca receiver shall be forked and added to the 5G-MAG repository. A change of the license is not possible due to the dependency to srsRAN

Hi,

Please specify in the Webinterface Installation instructions to change also the daemon user in rt-wui.service as it defaults to ofr (which is normally not available and it gives error).

It would be nice to have it set by default to fivegmag-rt since this is already added during the modem installation.

Thanks for the great work!

Installation Error - failed dependencies
Some of the libraries required can not be installed on an Ubuntu 20.04.2

To Reproduce
Steps to reproduce the behavior:
On a fress installation of Ubuntu 20.04 when I try to install the dependencies with this command
sudo apt install ssh g++ git libboost-atomic-dev libboost-thread-dev libboost-system-dev libboost-date-time-dev libboost-regex-dev libboost-filesystem-dev libboost-random-dev libboost-chrono-dev libboost-serialization-dev libwebsocketpp-dev openssl libssl-dev ninja-build libspdlog-dev libmbedtls-dev libboost-all-dev libconfig++-dev libsctp-dev libfftw3-dev vim libcpprest-dev libusb-1.0-0-dev net-tools smcroute python-psutil python3-pip clang-tidy gpsd gpsd-clients libgps-dev

Three of the packages fails to install

Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
clang-tidy : Depends: clang-tidy-10 (>= 10~) but it is not going to be installed
libboost-all-dev : Depends: libboost-python-dev but it is not going to be installed
libcpprest-dev : Depends: zlib1g-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Expected behavior
All dependency libraries get installed.

Desktop (please complete the following information):

• OS: Ubuntu 20.04.2
  $ uname -a
  Linux 5.11.0-40-generic #44~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

The reference client functionality should be extended to low latency support to enable low latency (LL) for LTE-based 5G terrestrial broadcast and to provide a comparable latency with LL OTT streams provided via CDN.

Is your feature request related to a problem? Please describe.

• The current gateway is not supporting low latency streams via 5G broadcast. Thus, the necessary changes on the gateway process, i.e. mainly the

Describe the solution you'd like

• Nginx support for LL-DASH and LL-HLS should be provided.
• End-2-end test with live setup (Origin - 5G BC core (R&S BSCC) - Transmitter - Receiver with gateway LL extension - open source LL player (e.g. DASH.js HLS.hs?) should be performed.

Which parts of the reference client are affected

• Gateway

Who takes care about the develepment

• Development will be done by ORS development resources.

ORS might be able to provide a node.js based control system for broadcast on demand and steering mechanisms

Description

Discussion and preparation of information material to be provided at the booth

• QR code for people to scan. Should link to a specific 5G-MAG website containing all relevant information
• Additional material? Flyers?

The sample files captured from the Lime SDR output contain RTP streams. In order to demonstrate HLS and DASH playback additional samples are required

Check and improve the documentation when running the modem as a service together with a BladeRF. The modem needs access the usb ports, the corresponding access rights need to be granted for the 5g-mag user.

Description

Our 5GMS stack supports Consumption Reporting. Add an end to end guide on how to do the setup and where to find the reports. This should go into the tutorials section of https://5g-mag.github.io/Getting-Started/pages/5g-media-streaming/tutorials.html

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Description

In the context of seamless switching we added multiple new configuration options to the rt-mbms-mw. This is to support the different Service Announcement formats and enable local testing via flute-ffmpeg. All this should be documented, ideally in a use-case oriented way.

Hi 5G-MAG expert group，

We use our own 5g broadcast transmitter to connect with 5gmag receiver . The 5gmag receiver works normally, but the IP packet cannot be obtained from Ethernet.

However, when we use sample file to receive, we can obtain IP packets in the same environment.

By comparing the log files generated by the two modes, it is found that the process has reached GW write_ pdu_ MCH function. There are both printing messages such as "RX MCH PDU...." and there is no error message about "DL TUN / TAP".

Attach file is contain syslog for two test mode. FIle “syslog_20220401_right“ is reported when using sample file and “syslog_20220401_wrong“ is reported when using SDR.
debug_log.zip

Please help to see where is the problem, thanks!

Description

For playback of 5GMS content on the client-side, information provided via the M8 interface is required. Our current implementation relies on an m8.json file with the following structure:

{
  "m5BaseUrl": "http://192.168.178.55:7778/3gpp-m5/v2/",
  "serviceList": [
    {
      "provisioningSessionId": "872a0eb2-e40a-41ed-bf2a-03b8343221a7",
      "name": "VoD: Llama Drama",
      "entryPoints": [
        {
          "locator": "http://192.168.178.55/m4d/provisioning-session-872a0eb2-e40a-41ed-bf2a-03b8343221a7/634cd01c-6822-4630-8444-8dd6279f94c6/CaminandesLlamaDrama4K.ism/manifest(format=mpd-time-csf)",
          "contentType": "application/dash+xml",
          "profiles": [
            "urn:mpeg:dash:profile:isoff-live:2011"
          ]
        },
        {
          "locator": "http://192.168.178.55/m4d/provisioning-session-872a0eb2-e40a-41ed-bf2a-03b8343221a7/634cd01c-6822-4630-8444-8dd6279f94c6/CaminandesLlamaDrama4K.ism/manifest(format=m3u8-aapl-v3)",
          "contentType": "application/vnd.apple.mpegurl"
        }
      ]
    }
  ]
}

Problem Description

Currently, only the msaf-configuration tool is capable of creating the m8.json file automatically. If the configuration of the AF is done via Postman, curl or any other REST client, the M8 information needs to be created manually and placed on a webserver for the 5GMS Aware Application to download.

Feature Request

Document how to create an m8.json file based on the configuration of the AF. Moreover, we should discuss if we can provide an endpoint to create the m8.json automatically similar to what the msaf-configuration tool is doing today.

In order to perform development work in the Gateway process without having to use the receiver it would be good to have multicast example streams available. The streams should be looped in order to enable longterm playback.

Is your feature request related to a problem? Please describe.
The receiver functionality should be extended to meet community requests for Rel16 features and to support features already available on the transmitter side.

Describe the solution you'd like

• SCS 0.37 kHz
• PBCH repetition
• Aggregation level 16
• CFI-indicator in MIB-MBMS
• CP 200 us
• CP 300 us

Which parts of the reference client are affected

• Receiver

Who takes care about the develepment

• Development will be done by ORS development resources.

The Obeca projects can be build and installed on a Linux machine. The aim is to support development and therefor successfully building and installing the components on MacOSX as well.

Description

The idea here is to have an informal face to face meeting of everyone involved in 5G-MAG acitvities. Decide on potential dates and create a Doodle poll.

Todos

• Present idea in next call
• Setup Doodle poll

IIs your feature request related to a problem? Please describe.
Broadcast on Demand

Describe the solution you'd like
implement a feedback loop to a control system to get information about how many users watching what from 5G BC and/or OTT. Based on actual usage and threshold value (users per service per region) the control system should dynamically (de-)provision services on the 5G BC core the xMB interface.

ToDo's:

• Implement (new) API between Gateway and Control System
• Implement Control System
• Implement xMB interface between Control System and BMSC
• Add (new, missing) xMB requests to signal service configuration, additional SA information, encryption

Which parts of the reference client are affected

• Gateway

Who takes care about the development

• Development will be done by ORS development resources.

Description

Our 5GMS stack supports QoE Metrics Reporting. Add an end to end guide on how to do the setup and where to find the reports. This should go into the tutorials section of https://5g-mag.github.io/Getting-Started/pages/5g-media-streaming/tutorials.html

I'm trying to replicate the setup for a minimalist use-case, software only. I've found the wiki and could clone and build most of the code (I haven't built everything to be honest). I was also present at the previous dev meetings. But I was not able to meet my ends. Did I miss something? Is it possible to address such a use-case?

Many thanks

Move the Wiki from https://github.com/Austrian-Broadcasting-Services/obeca-info/wiki to https://github.com/5G-MAG/Documentation-and-Architecture:

• Adjust the links in the Wiki
• Add table of content if missing
• Upload images

Description

Provide a description of the demo including

• Architecture diagram
• Concrete use case
• Story line. What do we want to tell at the booth

Additional questions

• Decide if we want to use a R&S transmitter and core system for the show

Description

• Provide a list of the required equipment to support the seamless switching demo use case

Description

Some questions need to be answered related to preparation of the booth:

• When do we start with the booth preparation and installation?
• Who needs access badges for the booth preparation
• How much space do we have at the booth? Is it sufficient for multiple screens?
• Do we need internet access? Might need to be ordered beforehand

Ubuntu 22.04 LTS was released on 21.04.2022: https://www.omgubuntu.co.uk/2022/04/ubuntu-22-04-lts-is-now-available-to-download

So far the 5G-MAG Reference Tools have offered support for Ubuntu 20.04. With the release of a new LTS we should check for 22.04 support and adjust the documentation accordingly if required.

The forked srsLTE dependency https://github.com/Austrian-Broadcasting-Services/srsLTE is out of sync with its parent repository https://github.com/srsran/srsRAN . In order to align the fork with its parent the best way is to apply the changes made in srsLTE on top of the current srsRAN version.

The Obeca project comes with a detailed instruction on how to implement the different components:
https://github.com/Austrian-Broadcasting-Services/obeca-info

One issue I encountered after the installation is that the receiver process can not send packets to the default network interface. The following error is shown:

DL TUN/TAP write error  Input/output error

My assumption is that the configuration is done correctly. I adjusted the /etc/default/opeca configuration in the following way:

# The tun interface to be created for the receive process
RP_TUN_INTERFACE="rp_tun"
RP_TUN_ADDRESS="192.168.180.10"

# Automatically set up multicast packet routing from the tun interface to a net>
ENABLE_MCAST_ROUTING=true
MCAST_ROUTE_TARGET="enp0s31f6"

based on:

$ nmcli device status
DEVICE     TYPE      STATE        CONNECTION         
enp0s31f6  ethernet  connected    Wired connection 1 
wlp3s0     wifi      unavailable  --                 
lo         loopback  unmanaged    --                 
rp_tun     tun       unmanaged    -- 

As part of this documentation we should provide clear instructions on how to the change the /etc/default/opeca configuration.

Description

This ticket is supposed to hold all relevant information for 5G media streaming over eMBMS.

Related specifications

• 26.501 - 5G Media Streaming (5GMS); General description and architecture (Release 16)
• 26.512 - 5G Media Streaming (5GMS); Protocols (Release 16)
• S4aI211256-Procedures - DRAFT CHANGE REQUEST for 26.501

Architecture diagrams

The Obeca flute library shall be moved to the 5G-MAG group using the 5G-MAG license.

We should make it more obvious that an SDR will never have the same capabilities as a real phone, for instance differences in noise-cancelling. The modem is a reference implementation, it is not intended to be used in production.

The Obeca gateway shall be moved to the 5G-MAG group using the 5G-MAG license

Hello,

I've tried to follow the instructions to disable BER calculations at the end of the installation instructions however it seems those work only for the old main branch, in the new one BER calculations aren't in the sch.c file, they have been removed and i couldn't follow from the print statement where they come from.
Do you know where can i find the BER calculations in the new branch to disable them?

Thanks

Several improvements for consideration:
In https://github.com/5G-MAG/Documentation-and-Architecture/wiki/Use-Case:-5G-Media-Streaming---End-to-End-Setup#3-running-the-application-server:
Add:

mkdir ~/.rt_5gms
cat > ~/.rt_5gms/application-server.conf <<EOF

EOF
mkdir -p /tmp/rt-5gms-as/cache
mkdir /tmp/rt-5gms-as/logs

so that the file is created with the right configuration or just specify the path to the application-server.conf (if already exist) and indicate the change of the m3listen to the local IP address.

In https://github.com/5G-MAG/Documentation-and-Architecture/wiki/Use-Case:-5G-Media-Streaming---End-to-End-Setup#4--running-the-application-function, in the "Creating a content hosting configuration", the output of ~/rt-5gms-application-function/install/bin/m1-session list -v should return the ipaddress specified in the yaml, right? In the previous part we changed it from localhost to 192.168.178.55. This should be the one listed. Just for consistency.

In Option 2 https://github.com/5G-MAG/Documentation-and-Architecture/wiki/Use-Case:-5G-Media-Streaming---End-to-End-Setup#2-starting-the-webserver, there may be some dependencies: install npm and some modules like npm install express

This is a container ticket that might get split into multiple sub-tickets. The goal is to setup a test environment for the different Obeca components and add unit, integration and functional tests. Before any implementation work is done we should agree on a test suite and how to implement the test cases.

Extend the existing documentation with a use case oriented documentation. Some ideas are:

• Standalone:
  • Play a RTP video
  • Play an HLS stream
  • Play a DASH stream
• Seamless Streaming:
  • Seamless streaming with changing availability of 5G BC and an OTT using a HLS stream
• Libraries: 
  • FLUTE encoding/decoding
  • ROUTE encoding/decoding
• Show and record basic signal Information

How to setup an end-to-end chain from the Core, to RAN to Client. Investigate which libraries can be used to implement

• Standalone core
• BMSC
• Any additional component

Describe the bug
Instructions for Webinterface in the Wiki do not reflect the updates to the rt-wui for the naming changes.

To Reproduce
Steps to reproduce the behavior:

1. Following the steps on the wiki will not work if you have followed the rt-wui README instructions

Expected behavior
Following the instructions on the wiki page should mirror those in the rt-wui README file

Screenshots
N/A

Desktop (please complete the following information):

• N/A

Smartphone (please complete the following information):

• N/A

Additional context
I re-wrote the rt-wui instructions in the README in line with the naming changes agreed in RT WG developers calls

I have attached a modified version of the relevant wiki page which will solve this Issue, it just needs to be renamed and replace the file Webinterface.md
rt-wui.md

Discuss and identify potential synergy with DVB-I activities.

• Service Lists, combine with 5G broadcast?
• Joint workshop to identify potential overlaps

The Obeca web interface shall be moved to the 5G-MAG group. It is to be clarified whether we can use the 5G-MAG contribution license. The internal dependencies of need to be verified, see package.json.

Investigate how to enable targeted ad insertion in 5G broadcast mode

Description

5GMS requires the integration of a Media Session Handler as defined in 26.512 - 5G Media Streaming (5GMS); Protocols (Release 16) :

We decided to focus on consumption reporting as the first main use case. Once a skeleton is in place additional features can be added.

Todos

Update the existing architecture diagram including the MSH.