The 5GMS Application Provider interacts with the 5GMS Application Function via M1 Provisioning interface, and uses M8 interface to communicate with UE.
In current implementation, SweetAlert window has been activated every time the creation of dynamic policies is attempted. It enables smooth input of every value, but doesn't contain any explanation on meaning of the parameters, or what is their purpose in overall mechanism. From the M1 Python library's documentation, it's clear that detailed information about structure of Dynamic Policies template can be found in TS 29.571 (Common Data Types for Service Based Interfaces).
Moreover, there is currently no client-side checking of inputed values, and the error handling is provided only by the backend code. The error message is just transpassed to the front GUI. This can be enhanced.
Solution
Include popover next to each parameter input field to provide supplemental information. Mark which fields are mandatory to create dynamic policy.
Additonally, add the client-side error handling layer to prevent input of wrong policies parameters. Limit the input to specifically required type, e.g. snssai.sd must be hexadecimal string etc. Instead of failed attempt to create policy template with wrong values, this layer will prevent attempt itself i.e. no function invokation if the parameters are not correctly formatted.
Note: Client-side in this context is considered to be front-end Javascript GUI.
Description
In current implementation,
SweetAlertwindow has been activated every time the creation of dynamic policies is attempted. It enables smooth input of every value, but doesn't contain any explanation on meaning of the parameters, or what is their purpose in overall mechanism. From the M1 Python library's documentation, it's clear that detailed information about structure of Dynamic Policies template can be found in TS 29.571 (Common Data Types for Service Based Interfaces).Moreover, there is currently no client-side checking of inputed values, and the error handling is provided only by the backend code. The error message is just transpassed to the front GUI. This can be enhanced.
Solution
Include popover next to each parameter input field to provide supplemental information. Mark which fields are mandatory to create dynamic policy.
Additonally, add the client-side error handling layer to prevent input of wrong policies parameters. Limit the input to specifically required type, e.g.
snssai.sdmust be hexadecimal string etc. Instead of failed attempt to create policy template with wrong values, this layer will prevent attempt itself i.e. no function invokation if the parameters are not correctly formatted.Note: Client-side in this context is considered to be front-end Javascript GUI.