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.9 KiB
web server interface principles
The web server interface is implemented in two parts: a back-end, included in the softmodem process and a front-end which is a browser application.
The oai web server back-end is implemented in a shared library to be loaded by the oai shared library loader when --websrv option is specified on the command line. libwebsrv.so code is common to all oai softmodem executables,
the current release has been tested with the nr UE and the gNB.
The front-end is an angular application. After being built and installed it is delivered to browsers by the back-end at connection time.
Front-end and back-end communicate via http request - http response transactions, including json body. these json interfaces are defined in the frontend/src/app/api/XXXX.api.ts files.
Back-end uses a callback machanism to map received http requests to dedicated functions. Typically a callback function decapsulates the http requests it receives, looking for the jsonbody to determine the requested information or command. Then the back-end builds a
http response, with a jsonbody encapsulating the requested information or the requested command result.
When unsolicited communication, from back-end to front-end is necessary, a websocket link is opened. This is the case for the softscope interface.
web server interface source files
web server source files are located in common/utils/websrv
- back-end files are directly located in the
websrvrepository - The frontend/src sub-directory contains the angular front-end source tree.
- common/utils/websrv/helpfiles contains files delivered to the front-end to respond to help requests.