resurrect meas_feed.c: vty, vty-test
At this point, meas-feed is usable again, however, osmo-bsc is not able to
include the IMSI in every report like osmo-nitb did.
In consequence, the meas-vis and meas-web tools are unable to handle the
current measurement reports: these so far use the IMSI to list reports, and all
reports without an IMSI are collapsed onto the same line, swapping values.
So though osmo-bsc now sends usable measurement reports via meas-feed, two
avenues to improve should be pursued:
OS#3192: the visualization tools should use bts,ts,ss numbers, not IMSI.
OS#2969: osmo-bsc should always know a mobile identity.
Related: OS#2968
Change-Id: I186c7a995dd2b81746c32a58b55da64ed195a1ce
2018-04-20 13:53:53 +00:00
|
|
|
#pragma once
|
2012-11-11 09:58:51 +00:00
|
|
|
|
|
|
|
#include <stdint.h>
|
|
|
|
|
2017-09-04 13:15:32 +00:00
|
|
|
#include <osmocom/bsc/meas_rep.h>
|
2012-11-11 09:58:51 +00:00
|
|
|
|
|
|
|
struct meas_feed_hdr {
|
|
|
|
uint8_t msg_type;
|
|
|
|
uint8_t reserved;
|
|
|
|
uint16_t version;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct meas_feed_meas {
|
|
|
|
struct meas_feed_hdr hdr;
|
|
|
|
char imsi[15+1];
|
|
|
|
char name[31+1];
|
|
|
|
char scenario[31+1];
|
|
|
|
struct gsm_meas_rep mr;
|
2015-08-21 00:48:39 +00:00
|
|
|
/* The logical channel type, enum gsm_chan_t */
|
|
|
|
uint8_t lchan_type;
|
|
|
|
/* The physical channel type, enum gsm_phys_chan_config */
|
|
|
|
uint8_t pchan_type;
|
2019-11-13 21:10:41 +00:00
|
|
|
/* number of this BTS in network */
|
2015-08-21 00:48:39 +00:00
|
|
|
uint8_t bts_nr;
|
|
|
|
/* number of this TRX in the BTS */
|
|
|
|
uint8_t trx_nr;
|
|
|
|
/* number of this timeslot at the TRX */
|
|
|
|
uint8_t ts_nr;
|
|
|
|
/* The logical subslot number in the TS */
|
|
|
|
uint8_t ss_nr;
|
2012-11-11 09:58:51 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
enum meas_feed_msgtype {
|
|
|
|
MEAS_FEED_MEAS = 0,
|
|
|
|
};
|
|
|
|
|
2015-08-21 00:48:39 +00:00
|
|
|
#define MEAS_FEED_VERSION 1
|
2012-11-11 09:58:51 +00:00
|
|
|
|
resurrect meas_feed.c: vty, vty-test
At this point, meas-feed is usable again, however, osmo-bsc is not able to
include the IMSI in every report like osmo-nitb did.
In consequence, the meas-vis and meas-web tools are unable to handle the
current measurement reports: these so far use the IMSI to list reports, and all
reports without an IMSI are collapsed onto the same line, swapping values.
So though osmo-bsc now sends usable measurement reports via meas-feed, two
avenues to improve should be pursued:
OS#3192: the visualization tools should use bts,ts,ss numbers, not IMSI.
OS#2969: osmo-bsc should always know a mobile identity.
Related: OS#2968
Change-Id: I186c7a995dd2b81746c32a58b55da64ed195a1ce
2018-04-20 13:53:53 +00:00
|
|
|
int meas_feed_cfg_set(const char *dst_host, uint16_t dst_port);
|
|
|
|
void meas_feed_scenario_set(const char *name);
|
2012-11-11 09:58:51 +00:00
|
|
|
|
resurrect meas_feed.c: vty, vty-test
At this point, meas-feed is usable again, however, osmo-bsc is not able to
include the IMSI in every report like osmo-nitb did.
In consequence, the meas-vis and meas-web tools are unable to handle the
current measurement reports: these so far use the IMSI to list reports, and all
reports without an IMSI are collapsed onto the same line, swapping values.
So though osmo-bsc now sends usable measurement reports via meas-feed, two
avenues to improve should be pursued:
OS#3192: the visualization tools should use bts,ts,ss numbers, not IMSI.
OS#2969: osmo-bsc should always know a mobile identity.
Related: OS#2968
Change-Id: I186c7a995dd2b81746c32a58b55da64ed195a1ce
2018-04-20 13:53:53 +00:00
|
|
|
void meas_feed_cfg_get(char **host, uint16_t *port);
|
|
|
|
const char *meas_feed_scenario_get(void);
|