Robert Schmidt
8107939f08
- all RAN code, CI code, configuration files, dockerfiles, in CSSL v1.0
- all deployment code (openshift, charts, ancillary files like shell
scripts), in MIT
- documentation in CC-BY-4.0
- exceptions might apply and are listed in NOTICE
- there is a new LICENSES folder with all licenses
- CONTRIBUTIONS.md has been updated accordingly
For automated changes based on OAI PL v1.1:
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.{c,h,cpp}
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.ts
perl -i~ -0pe 's/<!--.*Licensed to the OpenAirInterface.*openairinterface.org\n.*-->/<!-- SPDX-License-Identifier: LicenseRef-CSSL-1.0 -->/s' **/*.xml
The rest (cmake, files with missing license, cmake) manually.
1.0 KiB
1.0 KiB
Replay
First, read the basic usage to compile things.
Then, read record to know how to record a trace.
To replay, you use the replay program. It will act
as a tracee (lte-softmodem, nr-softmodem, etc.).
Then you use your usual tracer, eg. enb or textlog.
Since the T is constantly evolving you may need to extract
T_messages.txt contained in a trace to be able to process
the trace.
Example
Download example.raw. This example contains:
- MAC PDUs as sent and received by the eNodeB
- RRC info messages the eNodeB produced.
First step is to extract T_messages.txt from this trace.
./extract_config -i example.raw > extracted_T_messages.txt
Then you use replay to act as a regular tracee:
./replay -i example.raw
And then, while replay is still running, you use the tracer
you want, for example the textlog tracer:
./textlog -d extracted_T_messages.txt -no-gui -ON -full