... | ... | @@ -125,6 +125,13 @@ $ curl -XPOST localhost:9999/netstore/app/sample --data-binary @app_reconfigurat |
|
|
```
|
|
|
The application should show the following output:
|
|
|
```
|
|
|
[FLEXRAN_AGENT] application sample is running
|
|
|
[FLEXRAN_AGENT] reconfiguring app sample
|
|
|
[FLEXRAN_AGENT] print_param(): received 4 parameters
|
|
|
[FLEXRAN_AGENT] param key4 is true
|
|
|
[FLEXRAN_AGENT] param key1 is eins
|
|
|
[FLEXRAN_AGENT] param key3 is 1.123000
|
|
|
[FLEXRAN_AGENT] param key2 is 1
|
|
|
```
|
|
|
|
|
|
Regarding 2. and 3., have a look into the application source code in
|
... | ... | @@ -146,11 +153,11 @@ Suppose you configured OAI with two different PLMNs and core networks, one with |
|
|
PLMN 20895 and the other 20894. Furthermore, you configured two different
|
|
|
slices, 0 and 3, in both downlink and uplink direction. By configuring the imsi
|
|
|
application with the following JSON, you can have all UEs belonging to PLMN
|
|
|
20894 be associated to slice 3.
|
|
|
```JSON
|
|
|
20895 be associated to slice 3.
|
|
|
```json
|
|
|
{
|
|
|
"params" : {
|
|
|
"regex": { "str": "^20894" },
|
|
|
"regex": { "str": "^20895" },
|
|
|
"slice_dl": { "integer": 3 },
|
|
|
"slice_ul": { "integer": 3 },
|
|
|
}
|
... | ... | @@ -160,6 +167,20 @@ Configure using |
|
|
```bash
|
|
|
$ curl -XPOST localhost:9999/netstore/app/imsi --data-binary @imsi-reconfiguration.json
|
|
|
```
|
|
|
You should see the following output:
|
|
|
```
|
|
|
[FLEXRAN_AGENT] application imsi is running
|
|
|
[FLEXRAN_AGENT] reconfiguring app imsi
|
|
|
[FLEXRAN_AGENT] added new element to list: regex ^20895 slice DL 3 UL 3
|
|
|
[FLEXRAN_AGENT] RNTI ad43/IMSI 208950000000011 in the slice_dl 3
|
|
|
[FLEXRAN_AGENT] RNTI ad43/IMSI 208950000000011 in the slice_ul 3
|
|
|
[FLEXRAN_AGENT] RNTI 1b12/IMSI 208950000000002 in the slice_dl 3
|
|
|
[FLEXRAN_AGENT] RNTI 1b12/IMSI 208950000000002 in the slice_ul 3
|
|
|
```
|
|
|
|
|
|
Note that the imsi app is very bare-bones. Error handling is not properly done
|
|
|
yet, and in particular missing slices for a configuration will result in a
|
|
|
segfault.
|
|
|
|
|
|
# Reproducing the MobiCom demo
|
|
|
|
... | ... | |