WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
> _The following query endpoints and subscriptions will be supported in STF587, based on v1: (1) rab_info; (2) plmn_info; (3) cell_change; (4) rab_est; (5) rab_rel <br>- v2 changes for these endpoints are minor and may be considered during implementation or when v2 is available on Forge <br>- Remaining endpoints are either marked for STF587 Milestone D consideration (depending on time and effort) or deferred for future consideration beyond STF587. All RABs will have a consistent QCI value (e.g. non-GBR, QCI = 80 -- Low latency eMBB applications, TCP/UDP-based)_
The following query endpoints and subscriptions will be supported in STF587, based on v1: (1) rab_info; (2) plmn_info; (3) cell_change; (4) rab_est; (5) rab_rel.
This section describes how MEC012 has been integrated with the MEC Sandbox.
v2 changes for these endpoints are minor and may be considered during implementation or when v2 is available on Forge.
*Remaining endpoints are either marked for STF587 Milestone D consideration (depending on time and effort) or deferred for future consideration beyond STF587. All RABs will have a consistent QCI value (e.g. non-GBR, QCI = 80 -- Low latency eMBB applications, TCP/UDP-based)*
## MEC 012 v1.1.1 (available on forge)
@@ -38,10 +40,10 @@ References:
| /subscriptions/rab_est <br><br>_RAB establishment notification_ | Notifications report RAB establishments in the network, i.e. when a terminal connects to the 3GPP network. <br><br> Sandbox examples include: <ul><li> Terminal is added to the Macro Network Scenario by the user <li> Terminal connects to a 3GPP PoA after being connected to WiFi </ul><br>Supported filters include: <ul><li> plmnId: ignored <li> cellId: list of cell (if not present, RAB establishment on any cell) <li> QCI: ignored </ul><br> Expiry Deadline is ignored. <br><br> Notification returns: <ul><li> associateId: IPv4 address of the terminal <li> erabId: RAB Id for the terminal's bearer </ul> | As a Sandbox User, I can set a notification with no filters and I will get all RAB establishment events on any cell (terminal connection to 3GPP anywhere in the network). <br><br> As a Sandbox User, I can set a notification for a specific cell (or set of cells) and monitor RAB establishments for those cells. |
| /subscriptions/rab_mod <br><br>_RAB modification notification_ | Not supporting - future consideration beyond STF587 | Within the MEC Sandbox RABs will not change QCR, GBR or MBR. |
| /subscriptions/rab_rel <br><br>_RAB release notification_ | Notifications report RAB releases in the network, i.e. when a terminal disconnects from the 3GPP network. Sandbox examples include: <ul><li> Terminal is removed from the Macro Network Scenario by the user <li> Terminal disconnects from a 3GPP PoA and connects to WiFi (RAB is released). </ul><br> Supported filters include: <ul><li> erabId: single value (or associateId, list of IP addresses) <li> plmnId: ignored <li> cellId: list of cell (if not present, RAB release on any cell) <li> QCI: ignored </ul><br> Expiry Deadline is ignored. | As a Sandbox User, I can set a notification with no filters and I will get all RAB release events on any cell (terminal disconnect from 3GPP anywhere in the network - device removed or WiFi connection). <br><br> As a Sandbox User, I can get a RAB release notification for a specific terminal and I will get a notification, if that terminal disconnects from 3GPP. |
| subscriptions/meas_rep_ue <br><br>_Notification providing a UE measurement report (4G LTE), when available_ | *STF587 Milestone D consideration, depending on remaining time and effort*<br><br> Periodic events fit into MEC Sandbox scope (e.g. PERIODICAL_REPORT_STRONGEST_CELLS). Sandbox to trigger reports based on an internal period (not MEC app or Sandbox user configurable). <br><br> Trigger-based events not supported. | As a Sandbox user, I can set notifications to monitor UEs connected 4G LTE that include: signal levels, cell connection, and neighbor cells. |
| subscriptions/ta <br><br>_Notification providing a UE timing advance report_ | *STF587 Milestone D consideration, depending on remaining time and effort*<br><br> Sandbox to trigger TA reports based on an internal period (not MEC app or Sandbox user configurable). | Timing advanced calculated based on terminal distance from 3GPP PoA. <br><br> Applied to both 4G and 5G Cells. |
| subscriptions/ca_reconf <br><br>_Carrier aggregation reconfiguration notification_ | *Not supporting - future consideration beyond STF587* | Not supporting carrier aggregation emulation. Too detailed for MEC Sandbox |
| subscriptions/meas_rep_ue <br><br>_Notification providing a UE measurement report (4G LTE), when available_ | STF587 Milestone D consideration, depending on remaining time and effort <br><br> Periodic events fit into MEC Sandbox scope (e.g. PERIODICAL_REPORT_STRONGEST_CELLS). Sandbox to trigger reports based on an internal period (not MEC app or Sandbox user configurable). <br><br> Trigger-based events not supported. | As a Sandbox user, I can set notifications to monitor UEs connected 4G LTE that include: signal levels, cell connection, and neighbor cells. |
| subscriptions/ta <br><br>_Notification providing a UE timing advance report_ | STF587 Milestone D consideration, depending on remaining time and effort <br><br> Sandbox to trigger TA reports based on an internal period (not MEC app or Sandbox user configurable). | Timing advanced calculated based on terminal distance from 3GPP PoA. <br><br> Applied to both 4G and 5G Cells. |
| subscriptions/ca_reconf <br><br>_Carrier aggregation reconfiguration notification_ | Not supporting - future consideration beyond STF587 | Not supporting carrier aggregation emulation. Too detailed for MEC Sandbox |
| subscriptions/s1_bearer <br><br>_S1 bearer modification notification_ | Not supporting - future consideration beyond STF587| S1 Bearer too detailed for MEC Sandbox |
| subscriptions/nr_meas_rep_ue <br><br>_Notification providing a UE measurement report (5G NR), when available_ | STF587 Milestone D consideration, depending on remaining time and effort <br><br> Periodic events fit into MEC Sandbox scope (e.g. NR_PERIODICAL). Sandbox to trigger reports based on an internal period (not MEC app or Sandbox user configurable). <br><br> Trigger-based events not supported. | As a Sandbox user, I can set notifications to monitor UE when connected to 5G NR that include: signal levels, cell connection, and neighbor cells.
