Update MEC012.md - minor updates

| /subscriptions/RabEstSubscription	<br><br>_RAB establishment notification_	| Notifications report RAB establishments in the MEC Sandbox network, i.e. when a terminal connects to a 4G cell. <br><br> Sandbox examples include: <ul> <li> Terminal is added the MEC Sandbox by a user and it initially connects to a 4G macro cell <li> Terminal connects to a 4G PoA after being connected to WiFi or 5G </ul> <br>Supported filters (filterCriteriaQci) include: <ul> <li> cellId: list of cells (if not present, RAB establishment on any cell) <li> QCI: ignored <li> expiry deadline:  ignored </ul> <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 4G 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/RabModSubscription	<br><br>_RAB modification notification_ | Not supporting - future consideration beyond STF599 | Within the MEC Sandbox RABs will not change QCR, GBR or MBR. |

| /subscriptions/RabRelSubscription	<br><br>_RAB release notification_ | Notifications report RAB releases in the network, i.e. when a terminal disconnects from a 4G PoA. Sandbox examples include: <ul><li> Terminal is removed by the user from the Sandbox Scenario when it was connected to a 4G PoA. <li> Terminal disconnects from a 4G PoA and connects to WiFi or 5G (RAB is released consistent with 3GPP standards). </ul>  <br> Supported filters (filterCriteriaQci) include: <ul><li> erabId: single value (must be included in the request to identify the RAB) <li> cellId: list of cells (filters for specific cells, if not present, RAB release on any cell) <li> QCI: ignored <li> expiry deadline:  ignored </ul> <br> Notification returns: <ul><li> ecgi: 4G cell Id where the RAB was released <li> erabId: RAB Id for the released terminal's bearer </ul> |  <br><br> As a Sandbox User, I can set a RAB release notification for a specific terminal and I will get a notification, if that terminal disconnects from 4G. |

| subscriptions/MeasRepUeSubscription <br><br>_Notifications providing UE measurement reports (4G LTE), when available_ <br><br> _New STF599_ | Notification reports 4G UE measurements, including:  <ul><li> associateId list: UE's IPV4 address <li> ecgi: UE's primary serving 4G cell id (i.e. connected 4G cell) <li> rsrp: serving cell reference signal received power <li> rsrq: serving cell reference signal received quality <li> trigger: PERIODICAL_REPORT_STRONGEST_CELLS <li> 4G neighbor cell information (cell id, rsrp, rsrq) <li> 5G neighbor cell information (NR cell id, rsrp, rsrq) </ul> <br> Supported filters (filterCriteriaAssocTri) include: <ul><li> associateId: UE IPv4 address (if missing all UEs) <li> ecgi: list of cells (filters for specific cells; if not present, measurements on any serving cell) <li> trigger: ignored (only periodic strongest cell supported) <li> expiry deadline:  ignored </ul> | As a Sandbox user, I can set notifications to monitor UE measurements from connected 4G LTE cells that include:  serving cell id, serving cell signal levels, and neighbor cells.  <br><br> _Sandbox supports periodic events (e.g. PERIODICAL_REPORT_STRONGEST_CELLS). Sandbox triggers reports based on an internal period of 1 second (which is not MEC Application or Sandbox user configurable)._ <br><br> _RNIS specification improvement may be to include notification frequency, duration, and max instance filter criteria._ <br><br>  _MEC Sandbox network emulation prefers 5G cells over 4G cells.  As such, 5G neighbors may not be reported, as terminals will connect to 5G when detected in the network emulation._ |

| subscriptions/NrMeasRepUeSubscription <br><br>_Notification providing New Radio (NR) UE measurement reports (5G), when available_ <br><br> _New STF599_| Notification reports 5G NR UE measurements, including:  <ul><li> associateId: UE's IPV4 address <li> NR trigger: NR_PERIODICAL <li> 5G serving cell information: <ul><li> NR Cell Id <li> SSB reference signal received power <li> SSB reference signal received quality </ul> <li> Best neighbor cell info: <ul><li> SSB rsrp <li> SSB rsrq </li></ul> <li> 5G NR neighbor cell info list:  <ul><li> NR cell id <li> SSB rsrp <li> SSB rsrq </li></ul> <li> 4G neighbor cell info list:  <ul><li> 4G egci cell id <li> rsrp <li> rsrq </li></ul> </ul> <br> Supported filters (filterCriteriaNrMrs) include: <ul><li> associateId list: UE IPv4 address (if missing all UEs) <li> nrcgi: list of cells (filters for specific cells; if not present, measurements on any serving cell) <li> trigger: ignored (only NR periodic) <li> expiry deadline:  ignored </ul> | As a Sandbox user, I can set notifications to monitor UE measurements from connected 5G NR cells that include:  NR serving cell id, serving cell signal levels, and neighbor cells (4G and 5G). <br><br> _Sandbox supports periodic events (e.g. NR_PERIODICAL). Sandbox triggers reports based on an internal period of 1 second (which is not MEC Application or Sandbox user configurable)._ <br><br> _RNIS specification improvement may be to include notification frequency, duration, and max instance filter criteria._  |

| subscriptions/MeasRepUeSubscription <br><br>_Notifications providing UE measurement reports (4G LTE), when available_ <br><br> _New STF599_ | Notification reports 4G UE measurements, including:  <ul><li> associateId list: UE's IPV4 address <li> ecgi: UE's primary serving 4G cell id (i.e. connected 4G cell) <li> rsrp: serving cell reference signal received power <li> rsrq: serving cell reference signal received quality <li> trigger: PERIODICAL_REPORT_STRONGEST_CELLS <li> 4G neighbor cell information (cell id, rsrp, rsrq) <li> 5G neighbor cell information (NR cell id, rsrp, rsrq) </ul> <br> Supported filters (filterCriteriaAssocTri) include: <ul><li> associateId: UE IPv4 address (if missing all UEs) <li> ecgi: list of cells (filters for specific cells; if not present, measurements on any serving cell) <li> trigger: ignored (only periodic strongest cell supported) <li> expiry deadline:  ignored </ul> | As a Sandbox user, I can set notifications to monitor UE measurements from connected 4G LTE cells that include:  serving cell id, serving cell signal levels, and neighbor cells.  <br><br> _Sandbox supports periodic events (e.g. PERIODICAL_REPORT_STRONGEST_CELLS). Sandbox triggers reports based on an internal period of 1 second (which is not MEC Application or Sandbox user configurable)._ <br><br> _RNIS specification improvement may be to include notification frequency and max instance filter criteria._ <br><br>  _MEC Sandbox network emulation prefers 5G cells over 4G cells.  As such, 5G neighbors may not be reported, as terminals will connect to 5G when detected in the network emulation._ |

| subscriptions/NrMeasRepUeSubscription <br><br>_Notification providing New Radio (NR) UE measurement reports (5G), when available_ <br><br> _New STF599_| Notification reports 5G NR UE measurements, including:  <ul><li> associateId: UE's IPV4 address <li> NR trigger: NR_PERIODICAL <li> 5G serving cell information: <ul><li> NR Cell Id <li> SSB reference signal received power <li> SSB reference signal received quality </ul> <li> Best neighbor cell info: <ul><li> SSB rsrp <li> SSB rsrq </li></ul> <li> 5G NR neighbor cell info list:  <ul><li> NR cell id <li> SSB rsrp <li> SSB rsrq </li></ul> <li> 4G neighbor cell info list:  <ul><li> 4G egci cell id <li> rsrp <li> rsrq </li></ul> </ul> <br> Supported filters (filterCriteriaNrMrs) include: <ul><li> associateId list: UE IPv4 address (if missing all UEs) <li> nrcgi: list of cells (filters for specific cells; if not present, measurements on any serving cell) <li> trigger: ignored (only NR periodic) <li> expiry deadline:  ignored </ul> | As a Sandbox user, I can set notifications to monitor UE measurements from connected 5G NR cells that include:  NR serving cell id, serving cell signal levels, and neighbor cells (4G and 5G). <br><br> _Sandbox supports periodic events (e.g. NR_PERIODICAL). Sandbox triggers reports based on an internal period of 1 second (which is not MEC Application or Sandbox user configurable)._ <br><br> _RNIS specification improvement may be to include notification frequency and max instance filter criteria._  |

| subscriptions/MeasTaSubscription <br><br>_Notification providing a UE timing advance report_ | _Not supporting - future consideration beyond STF599_ | Timing advanced can be emulated in the MEC Sandbox calculated based on terminal distance from a 4G PoA.  |

| subscriptions/CaReconfSubscription <br><br>_Carrier aggregation reconfiguration notification_ | _Not supporting - future consideration beyond STF599_ | Not supporting carrier aggregation emulation.  Too detailed for MEC Sandbox |

| subscriptions/S1BearerSubscription <br><br>_S1 bearer modification notification_ | _Not supporting - future consideration beyond STF599_ | S1 Bearers are not modeled or emulated in the MEC Sandbox. |