Datasets:

GSMA
/

camara

Item	Details
Summary	As an application developer, I want my application to comply with current restrictions applicable based on the service status, network conditions, and location
Roles, Actors and Scope	Roles: Customer:User Actors: Mobile Network Operators (MNO), [Entprerise] Application developers. Scope: Any device serviced by MNO
Pre-conditions	The preconditions are listed below: Application developer has been onboarded to MNO MNO offeres Capabilities and Runtime Restrictions APIs Application developer has subscribed to Capabilities and Runtime Restriction APIs As necessary, customer consent has been secured Application developer has implemented Capabilities and Runtime Restriction API
Activities/Steps	Starts when: Presumably upon mobile application client session start. Application makes a request to retreieve the list of capabilities, their status (enabled/disabled), and restrictions that are applicable to those enabled services, given a particular client. Ends when: MNO returns the capabilities and runtime restrictions applicable to the request.
Post-conditions	Application may adjust UI elements according to the current restrictions. The Application, when sending a request to the CAMARA API, can ensure / adjusts information according to the restrictions. MNO may maintain a cache of the capabilities and restrictions sent in response to Application request.
Exceptions	Several exceptions might occur: Unauthorized: Not valid credentials Not found: Client identifier is not managed by the MNO Invalid Input: Request is not properly structured, or missing mandatory input data Service not available: Capabilities and Runtime Restrictions service is [temporarily] not available

User Story: Capabilities and Runtime Restrictions - Subscription

Item	Details
Summary	As an application developer, I want my application to comply with current restrictions applicable based on the service status, network conditions, and location. I want my application to subscribe to any changes in capabilities and restrictions
Roles, Actors and Scope	Roles: Customer:User Actors: Mobile Network Operators (MNO), [Entprerise] Application developers. Scope: Any device serviced by MNO
Pre-conditions	The preconditions are listed below: Application developer has been onboarded to MNO MNO offeres Capabilities and Runtime Restrictions APIs Application developer has subscribed to Capabilities and Runtime Restriction APIs As necessary, customer consent has been secured Application Client or the Application Backend server has implemented Capabilities and Runtime Restriction API
Activities/Steps	Start when: Presumably upon mobile application client session start. Application makes a request to receive the current the list of capabilities, their status (enabled/disabled), and restrictions that are applicable to those enabled services and subscribe to any changes after the intial push. Continues with: Any changes in capabilities or runtime restrictions change sent as an event notification to subscribed Application Application may adjust UI elements according to the current restrictions. The Application, when sending a request to the CAMARA API, can ensure / adjusts information according to the restrictions. Ends when: Subscrption expires, or subscribing entity terminates the subscription
Post-conditions	MNO may maintain a cache of the capabilities and restrictions responded with. Application client may enable/disable UI components based on restricted services at time. Application client validates, localy or with the Application backend server, Service API prior to making a request to the MNOs Service API endpoint, and avoids any failures.
Exceptions	Several exceptions might occur: Unauthorized: Not valid credentials Not found: Client identifier is not managed by the MNO Invalid Input: Request is not properly structured, or missing mandatory input data Service not available: Capabilities and Runtime Restrictions service is [temporarily] not available