TI API: user mobility problem

[FabrizioMoggio]

Problem description
The TI API can be invoked for any user or for specific users. Currently if the API is invoked for any user and than it is invoked for a specific user, the "any user intent" is automatically deleted and the network is optimized only for the specifically requested users. This doesn't work with user mobility when I invoke the API for any user but then I detect that a user is moving among geographical areas. To optimize the network for that user I invoke the TI API for that user specifically and the system automatically delete the "any user intent". This behavior is not correct.

Expected behavior
The "any user intent" must be manually deleted by the API Consumer.

Use Case 1: optimization for any user while supporting user mobility

• TI API invoked for any user. Any user attached to an Edge UPF is routed to the Edge Application
• TI API invoked for the user that is moving. the user is moved to the closest UPF in that area
• The network is anyway configured to support any user

Use Case 2: after a trial phase where every user is optimized, just some selected user are optimized

• TI API invoked for any user (trial phase)
• TI API invoked to delete the "any user" intent
• TI API invoked for the selected users
• The network is optimized only for the selected users

Required Action
Modification of the TI API documentation

[FabrizioMoggio]

Fixed with: #315