Use cases
It is scenario based Use Cases which describes interaction of User with System. Each separate Use Case is focused on achieving one particular Goal. Scenarios in scope of single Use Case describe possible variation and erroneous path in the Goal achievement.
Use case #1: New account is created in PortaBilling; the account is assigned to a SIM card from inventory.
Roles: HSS, SPR, PortaBilling system (PB), PB administrator, Portal, end user.
Preconditions:
- A SIM is supplied to the end user.
- SIM ids are uploaded to the device inventory of PortaBilling.
- Product with LTE service is created.
- Product without LTE service is created.
Use scenario #1.1 Successful provisioning
Scenario:
- PB administrator/Portal assigns SIM from the inventory to the account with activation and expiration dates, the associated product which includes LTE internet access service, subscriptions, etc.
- PB handles the event by provisioning(i.e. sending) specific data to HSS and then to SPR
- HSS handles request from PortaBilling and applies required changes in EPC.
- SPR handles request from PortaBilling and applies required changes in EPC.
- HSS is now able to authenticate new SIM on the user equipment.
- The end user is now able to get the service according to the configuration in SPR.
- PB administrator/Portal assigns SIM from the inventory to the account with activation and expiration dates, the associated product does NOT include LTE internet access service
No provisioning to HSS and SPR is required
- The end user is not able to get the LTE internet access service.
PB administrator/Portal creates the account with activation and expiration dates, the associated subscriptions, product which does NOT include LTE internet access service.
No provisioning to HSS and SPR is required
- The end user is not able to get the LTE internet access service.
Use case #2: Account is terminated/blocked/suspended/credit exceeded in PortaBilling.
Roles: HSS, SPR, PortaBilling system (PB), PB administrator, Portal, end user.
Preconditions:
- A SIM is supplied to the end user.
- SIM ids are uploaded to the device inventory of PortaBilling.
- Product with LTE service is created.
- The end user is subscribed and uses LTE service according to the product above.
Use scenario #2.1: Successful termination
Scenario:
- PB administrator/Portal terminates the account with the associated product which includes LTE internet access service, subscriptions, etc.
- PB handles the event by provisioning(i.e. sending) specific data to HSS and then to SPR
- HSS handles request from PortaBilling and applies required changes in EPC.
- SPR handles request from PortaBilling and applies required changes in EPC.
- HSS is now not able to authenticate the SIM on the user equipment.
- The end user is now not able to get the service.
Use scenario #2.2: Successful block
Scenario:
- PB administrator/Portal blocks the account with activation and expiration dates, the associated subscriptions, product which includes LTE internet access service.
- PB system handles the event by provisioning(i.e. sending) specific data to HSS
- No provisioning to SPR is required.
- HSS handles request from PortaBilling and applies required changes in EPC.
- The end user is now not able to get the service. Service usage will be prevented by HSS when user tries to connect.
Use scenario #2.3: Successful unblock
Scenario:
- PB administrator/Portal unblocks the account with activation and expiration dates, the associated subscriptions, product which includes LTE internet access service.
- PB system handles the event by provisioning(i.e. sending) specific data to HSS
- No provisioning to SPR is required.
- HSS handles request from PortaBilling and applies required changes in EPC.
- The end user is now able to get the service according to the configuration in SPR.
Use scenario #2.4: Successful suspension
Scenario:
- PB system suspends the account with activation and expiration dates, the associated subscriptions, product which includes LTE internet access service.
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is redirected to captive portal. Service usage will be prevented by SPR when user tries to connect.
Use scenario #2.5: Successful unsuspension
Scenario:
- PB system unsuspends the account with activation and expiration dates, the associated subscriptions, product which includes LTE internet access service.
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is now able to get the service according to the configuration in SPR.
Use scenario #2.6: No available funds
Scenario:
- The user customer/account exceeds the credit limit
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is redirected to captive portal. Service usage will be prevented by SPR when user tries to connect.
Use scenario #2.7: Available finds appear
Scenario:
- The user puts available funds to his/her customer/account with activation and expiration dates, the associated subscriptions, product which includes LTE internet access service.
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is now able to get the service according to the configuration in SPR.
Use case #3: Product changes
Roles: HSS, SPR, PortaBilling system (PB), PB administrator, Portal, end user.
Preconditions:
- A SIM is supplied to the end user.
- SIM ids are uploaded to the device inventory of PortaBilling.
- Product X with LTE service is created.
- Product Y with non-LTE service is created.
- Product Z with LTE service is created.
- The end user is subscribed and uses LTE service according to the product X.
Use scenario #3.1: LTE to non-LTE (X to Y)
Scenario:
- PB administrator changes the product from X to Y, the one which doesn’t include LTE internet access service.
- All the following steps and provisioning are identical to Use scenario #2.1.
PB administrator assigns SIM from the inventory to the account with activation and expiration dates, and changes the product to X, the one which includes LTE internet access service.
- All the following steps and provisioning are identical to Use scenario #1.1.
Use scenario #3.3: LTE to LTE with different access policies (X to Z)
- PB administrator changes the product from X to Z, the one which includes LTE service with different access policy.
- PB handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- Subscriber in SPR is assigned different service policy.
- The end user is now able to use the service according to the new internet access policy.
Use scenario #3.4: Internet access policy is changed directly on account
- PB administrator changes the internet access policy directly on account with LTE product Z.
- All the following steps and provisioning specification are identical to Use scenario #3.3.
Use case #4: Mobile account identity changes
Roles: HSS, SPR, PortaBilling system (PB), PB administrator, Portal, end user.
Preconditions:
- A SIM is supplied to the end user.
- SIM ids are uploaded to the device inventory of PortaBilling.
- Product with LTE service is created.
- The end user is subscribed and uses LTE service according to the product above.
Use scenario #4.1: Account ID changed for an account
Scenario:
- PB administrator/Portal changes the ID of the account with the associated product which includes LTE internet access service, subscriptions, etc.
- PB system handles the event by provisioning(i.e. sending) specific data to HSS and then to SPR
- HSS handles request from PortaBilling and applies required changes in EPC.
- SPR handles request from PortaBilling and applies required changes in EPC.
- HSS is able to authenticate the SIM on the user equipment.
- The end user is able to get the service.
Use scenario #4.2: Account has been provisioned to a different SIM card (linked to a different IMSI)
Scenario:
- PB administrator/Portal changes the SIM card for the account.
- PB system handles the event by provisioning(i.e. sending) specific data to HSS
- HSS handles request from PortaBilling and applies required changes in EPC.
- SPR handles request from PortaBilling and applies required changes in EPC.
- HSS is able to authenticate the SIM on the user equipment.
- The end user is able to get the service.
Use case #5: Account top-up
Roles: HSS, SPR, PortaBilling system (PB), PB administrator, Portal, end user.
Preconditions:
- A SIM is supplied to the end user.
- SIM ids are uploaded to the device inventory of PortaBilling.
- Product with LTE service is created.
- The end user is subscribed and uses LTE service according to the product above.
Use scenario #5.1: Time-based allotment top-up
Scenario:
- PB administrator/Portal changes the Activation/Expiration date of the account with the associated product which includes LTE internet access service, subscriptions, etc.
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is now able to get the service according to the configuration in SPR.
Use scenario #5.2: Volume-based allotment top-up
Scenario:
- PB administrator/Portal changes the Product for the account with the associated product which includes LTE internet access service, subscriptions, etc.
- PB system handles the event by provisioning(i.e. sending) specific data to SPR
- No provisioning to HSS is required.
- SPR handles request from PortaBilling and applies required changes in EPC.
- The end user is now able to get the service according to the configuration in SPR.
Use scenario #5.3: Prepaid account balance top-up
Scenario:
- The end user pays by credit card to top-up the balance of his/her prepaid account via self-care Portal.
- The end user uses those funds to buy and pay for a one-time-billed Time-based or Data-Volume-Based plans as desired from the Captive Portal/self-care page. Initial “True Prepaid” plans will not auto-renew just because funds are available.
- All the following steps and provisioning specification correspond to either Use scenario #5.1 or Use scenario #5.2.