diff --git a/documentation/API_documentation/Device Identifier User Story.md b/documentation/API_documentation/Device Identifier User Story.md index 39c9ca4..99720b0 100644 --- a/documentation/API_documentation/Device Identifier User Story.md +++ b/documentation/API_documentation/Device Identifier User Story.md @@ -2,7 +2,7 @@ | **Item** | **Details** | | ---- | ------- | -| ***Summary*** | As an application developer belonging to an enterprise, I want my application server to be able to request the identity of the mobile device (represented by the IMEI) currently being used by a given mobile network subscriber (identified by MSISDN, NAI or IP address). Optionally, I'd like to know the make and model of that device. | +| ***Summary*** | As an application developer belonging to an enterprise, I want my application server to be able to request the identity of the mobile device (represented by the IMEI) currently being used by a given mobile network subscriber (identified by MSISDN, IP address or, when supported by network operators, a Network Access Identifier). Optionally, I'd like to know the make and model of that device. | | ***Roles, Actors and Scope*** | **Roles:** Customer:User
**Actors:** Application Service Providers, Hyperscalers, Application Developers, End Users
**Scope:** *Order To Activate (OTA)* \- Retrieve device identifier details | | ***Pre-Conditions*** |The preconditions are listed below:
  1. The Customer:BusinessManager and Customer:Administrator have been onboarded to the CSP's API platform.
  2. The Customer:BusinessManager has successfully subscribed to the Device Identifier product from the product catalog.
  3. The Customer:Administrator has onboarded the Customer:User to the platform.
  4. The Customer:BusinessManager has agreed to the terms and conditions of the CSP for managing consent of mobile subscription owners.
  5. The means to get the access token are known to the Customer:User to ensure secure access of the API.| | ***Activities/Steps*** | **Starts when:** The Customer:User's application server makes a POST request to the Device Identifier API containing the end user's subscription information in the request body in order to retrieve the device identifier plus any optional device information.
    **Ends when:** The Device Identifier API returns the requested information, or an error message | @@ -13,7 +13,7 @@ | **Item** | **Details** | | ---- | ------- | -| ***Summary*** | As an application developer belonging to an enterprise, I want my application server to be able to request details about the type of the mobile device (represented by the Type Approval Code - TAC) currently being used by a given mobile network subscriber (identified by MSISDN, NAI or IP address). Optionally, I'd like to know the make and model of that device. | +| ***Summary*** | As an application developer belonging to an enterprise, I want my application server to be able to request details about the type of the mobile device (represented by the Type Approval Code - TAC) currently being used by a given mobile network subscriber (identified by MSISDN, IP address or, when supported by network operators, a Network Access Identifier). Optionally, I'd like to know the make and model of that device. | | ***Roles, Actors and Scope*** | **Roles:** Customer:User
    **Actors:** Application Service Providers, Hyperscalers, Application Developers, End Users
    **Scope:** *Order To Activate (OTA)* \- Retrieve device type details | | ***Pre-Conditions*** |The preconditions are listed below:
    1. The Customer:BusinessManager and Customer:Administrator have been onboarded to the CSP's API platform.
    2. The Customer:BusinessManager has successfully subscribed to the Device Type product from the product catalog.
    3. The Customer:Administrator has onboarded the Customer:User to the platform.
    4. The Customer:BusinessManager has agreed to the terms and conditions of the CSP for managing consent of mobile subscription owners.
    5. The means to get the access token are known to the Customer:User to ensure secure access of the API.| | ***Activities/Steps*** | **Starts when:** The Customer:User's application server makes a POST request to the Device Type API containing the end user's subscription information in the request body in order to retrieve the device TAC plus any optional device information.
      **Ends when:** The Device Type API returns the requested information, or an error message |