| [/queries/ap/ap_information](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.1.1/WlanInformationApi.yaml#/wai/apInfoGET)<br><br> This resource is queried to retrieve information on WLAN Access Points in the network. | GET method is used to query for all access points in the network, or sub-sets based on Access Point identity (MAC Address), SSID, etc. <br><br> WLAN AP's uniquely identified via MAC Address. <br><br> All APs share the same SSID. <br><br> "filter" (attribute-based filtering pattern from MEC009) expression used to select queries for specific APs (based on MAC Address) or group of APs (based on SSID). <br><br> Returns WiFi AP list: <ul><li> AP identity (MAC address) <li> AP location (geo-location) <li> BSS load (counted STA count) </li></ul> | As a Sandbox user, I can use this call to learn about all the WLAN Hotspots in the network, including for each AP: identity (MAC Address and SSID), # of connected terminals, BSS Load, geolocation, etc. I do not need to know anything about the AP's and I can discovery them. Filter input = null. <br><br><br> As a Sandbox user, I can use this call to query status of a specific AP (if I know the AP MAC Address). For example, to learn the AP's current BSS Load, including # of connected STAs. |
| [/queries/sta/sta_information](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.1.1/WlanInformationApi.yaml#/wai/staInfoGET)<br><br> This resource is queried to retrieve information on terminals (STA) connected to WLAN Access Points in the network. <br><br> _STF 599 updated (WLAN signal level - RSSI signal emulation)_ | GET method is used to query and discover all terminals connected to WLAN. Alternatively, it can be used to query the current status of a terminal (STA), based on MAC Address or IPv4 Address. <br><br> Terminals maintain a consistent IPv4 Address between 3GPP cellular (4G or 5G) and WLAN access connections, following the 3GPP trusted non-3GPP access model. <br><br> "filter" (attribute-based filtering pattern from MEC009) expression used to select queries for specific STA's (based on MAC Address or IPv4 Address). <br><br> Returns a list of WLAN connected terminal devices: <ul><li> STA Id (MAC address, IPv4 address) <li> Connected AP Id (MAC address) <li> WiFi signal level (RSSI) </li></ul> | As a Sandbox user, I can use this call to learn about all the terminals that are connected to WLAN Hotspots in the network, including for each STA: it's identity (STA MAC Address and IPv4 Address), connected AP (AP MAC Address and SSID), signal level in RSSI (calculated based on distance from AP in Sandbox). I do not need to know anything about the STA's and I can discover them. Filter input = null. <br><br><br> As a Sandbox user, I can use this call to query status of a specific terminal (if I know the STA's MAC Address or IPv4 Address). For example, to learn current RSSI signal level or connected AP status. |
| [/queries/ap/ap_information](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.2.1/WlanInformationApi.yaml#/wai/apInfoGET)<br><br> This resource is queried to retrieve information on WLAN Access Points in the network. | GET method is used to query for all access points in the network, or sub-sets based on Access Point identity (MAC Address), SSID, etc. <br><br> WLAN AP's uniquely identified via MAC Address. <br><br> All APs share the same SSID. <br><br> "filter" (attribute-based filtering pattern from MEC009) expression used to select queries for specific APs (based on MAC Address) or group of APs (based on SSID). <br><br> Returns WiFi AP list: <ul><li> AP identity (MAC address) <li> AP location (geo-location) <li> BSS load (counted STA count) </li></ul> | As a Sandbox user, I can use this call to learn about all the WLAN Hotspots in the network, including for each AP: identity (MAC Address and SSID), # of connected terminals, BSS Load, geolocation, etc. I do not need to know anything about the AP's and I can discovery them. Filter input = null. <br><br><br> As a Sandbox user, I can use this call to query status of a specific AP (if I know the AP MAC Address). For example, to learn the AP's current BSS Load, including # of connected STAs. |
| [/queries/sta/sta_information](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.2.1/WlanInformationApi.yaml#/wai/staInfoGET)<br><br> This resource is queried to retrieve information on terminals (STA) connected to WLAN Access Points in the network. <br><br> _STF 599 updated (WLAN signal level - RSSI signal emulation)_ | GET method is used to query and discover all terminals connected to WLAN. Alternatively, it can be used to query the current status of a terminal (STA), based on MAC Address or IPv4 Address. <br><br> Terminals maintain a consistent IPv4 Address between 3GPP cellular (4G or 5G) and WLAN access connections, following the 3GPP trusted non-3GPP access model. <br><br> "filter" (attribute-based filtering pattern from MEC009) expression used to select queries for specific STA's (based on MAC Address or IPv4 Address). <br><br> Returns a list of WLAN connected terminal devices: <ul><li> STA Id (MAC address, IPv4 address) <li> Connected AP Id (MAC address) <li> WiFi signal level (RSSI) </li></ul> | As a Sandbox user, I can use this call to learn about all the terminals that are connected to WLAN Hotspots in the network, including for each STA: it's identity (STA MAC Address and IPv4 Address), connected AP (AP MAC Address and SSID), signal level in RSSI (calculated based on distance from AP in Sandbox). I do not need to know anything about the STA's and I can discover them. Filter input = null. <br><br><br> As a Sandbox user, I can use this call to query status of a specific terminal (if I know the STA's MAC Address or IPv4 Address). For example, to learn current RSSI signal level or connected AP status. |
### Subscription Endpoints
> Within WAIS all subscription types are managed under a single _/subscriptions_ endpoint. For readability, the following table presents each subscription type in a separate listing. However, they are all managed under the GET, POST, PUT, and DELETE methods for _/subscriptions_ and _/subscriptions/{subscriptionId} endpoints._ <br><br> The MEC Sandbox does not support subscription expiry deadlines or notifications.
| [/subscriptions](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.1.1/WlanInformationApi.yaml#/wai/subscriptionLinkList_subscriptionsGET)<br><br> GET method is used to request information about the subscriptions for this requestor. Upon success, the response contains entity body with the list of links to the subscriptions that are present for the requestor <br><br> _STF 599 updated_ | Return list of all WAIS subscriptions | /subscriptions/{subscriptionId} returns the subscription information for a specific subscription. |
| [/subscriptions](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.1.1/WlanInformationApi.yaml#/wai/subscriptionsPOST)<br><br> POST method is used create a notification subscription instance. Upon success, the response contains entity body of the created subscription (including its unique subscriptionId). <br><br> _STF 599 updated_ | Utilized to create subscriptions in RNIS. | With the subscriptionId, /subscriptions/{subscriptionId}: <ul><li> PUT method: updates the subscription </li><li> DELETE: removes the subscription </li></ul> MEC Sandbox supports the AssocStaSubscription. <br><br> StaDataRateSubscription and MeasurementReportSubscription types are not supported as detailed later in this table. |
| [/subscriptions](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.2.1/WlanInformationApi.yaml#/wai/subscriptionLinkList_subscriptionsGET)<br><br> GET method is used to request information about the subscriptions for this requestor. Upon success, the response contains entity body with the list of links to the subscriptions that are present for the requestor <br><br> _STF 599 updated_ | Return list of all WAIS subscriptions | /subscriptions/{subscriptionId} returns the subscription information for a specific subscription. |
| [/subscriptions](https://forge.etsi.org/swagger/ui/?url=https://forge.etsi.org/rep/mec/gs028-wai-api/raw/v2.2.1/WlanInformationApi.yaml#/wai/subscriptionsPOST)<br><br> POST method is used create a notification subscription instance. Upon success, the response contains entity body of the created subscription (including its unique subscriptionId). <br><br> _STF 599 updated_ | Utilized to create subscriptions in RNIS. | With the subscriptionId, /subscriptions/{subscriptionId}: <ul><li> PUT method: updates the subscription </li><li> DELETE: removes the subscription </li></ul> MEC Sandbox supports the AssocStaSubscription. <br><br> StaDataRateSubscription and MeasurementReportSubscription types are not supported as detailed later in this table. |
| /subscriptions/AssocStaSubscription <br><br>_WLAN event notifications about associated stations (terminals)._<br><br> _STF 599 updated_ | Sandbox issues this notification on a change in STA connections on an AP basis (whenever a STA connects or disconnects from the AP). <br><br> Subscriptions must be created individually on an AP by AP basis (one AP per subscription instance per the spec data model) <br><br> Subscription input includes: <ul><li> AP Id (must be included) <li> notification period (optional) <li> notification trigger threshold (optional) <li> notification callback URI <li> alternative, WebSocket notification configuration </li></ul> Notification returns: <ul><li> AP Id (MAC Address and SSID) <li> List of connected terminals (STA Id - MAC address and IPV4 address) </ul> | As a Sandbox user, I can use this notification subscription to monitor connections on WLAN access points of interest. <br><br> After learning from this notification that a STA is connected to a specific AP, I can: <ul><li> Query ap_information to see how busy the AP may be (via BSS Load); <li> Query sta_information to check the WLAN signal level (via RSSI) of the STA.
| /subscriptions/StaDataRateSubscription <br><br>_WLAN event notification about a STA (terminal data rates)_ | Not supporting - future consideration beyond STF599 | The MEC Sandbox is not emulating data traffic from terminals. |
| /subscriptions/MeasurementReportSubscription <br><br>_WLAN event notification about STA measurement reports (channel load, beacon request, STA statistics, neighbor report)_ | Not supporting - future consideration beyond STF599 | STA measurement reports and configuration are too detailed for the MEC Sandbox network emulation capability.|
### Measurement Endpoints
> Measurement configuration endpoints were recently introduced into the WAIS. These endpoints are used to configure detailed, STA specific radio-level measurements, whose measurement reports are then available in the _/queries/sta/sta_information_ query or reported in _MeasurementReportNotification_ notifications. These reports and their configuration are low-level IEEE standard measurements and beyond the network emulation capabilities of the MEC Sandbox.
