9 Charging
22.2403GPPRelease 17Service requirements for 3GPP Generic User Profile (GUP)Stage 1TS
It shall be possible to support charging for the management, access and synchronization of the 3GPP Generic User Profile. (e.g. for capability negotiation or remote diagnostic information gathering).
Note: There might be legislative restrictions on charging. This is FFS.
Annex A (informative):
Example 3GPP Generic User Profile use cases
- Setting up a Subscription for a new customer
- Precondition
- A person has just purchased a new device, and requires new subscription data to be initiated in the shop.
- Actions
- Subscription data is input by the shop personnel by means of a Subscription Management application.
- Subscription Management application stores the data in Generic User Profile in the Home Network.
- Post-condition
- The user can leave the shop. Her subscription is ready to use.
2. Application Access to User Profile Data using OSA (Pull Scenario)
- Precondition
- The application is registered with the OSA framework
- The application is authorised to access the user profile management Service Control Function and use methods which permit read/write data in user profiles
- Actions
- The application uses OSA to read/write data in the user profile of the user
- The network provides the requested data or modifies the data as requested
- Post-condition
- Consistency of the user profile data
3. Notification of user subscription to an HE-VASP application using OSA (Push Scenario)
- Precondition
- The OSA application from the HE-VASP is registered with the OSA framework
- The OSA application is authorized to receive subscription/unsubscription notifications
- The OSA application has subscribed to the notification permitting to it to know when new users have subscribed to the service implemented by the OSA application
- Actions
- A new user subscribes to the service implemented by the OSA application
- The Home Environment notifies the OSA application about a new subscription and provides it with relevant information (e.g. identity of the user)
- Possibly the OSA application provides the home environment with a link (e.g. URL) to a location where the user can customize the service
- Post-conditions
- The OSA application can now have access to home environment -owned user profile information for this user, provided that it is granted the related access rights
- The user can customize service data for the service implemented by the OSA application
4. Customization of service specific data for a VHE service provided by a HE-VASP
- Preconditions
- The user has a VHE subscription
- The user is subscribed to the service provided by the HE-VASP
- There is a link from the user Personal Service Environment (PSE) to the HE-VASP for service customization
- The user has access to her PSE and has successfully been logged to it
- Actions
- The user accesses her PSE and decides to customize the service provided by the HE-VASP
- She transparently access a service customization interface provided by the HE-VASP (possibly via a hyperlink)
- She defines/modifies service customization data, which are managed and stored by the HE-VASP
- Post-condition
- Next time she uses the service, new customization data will be used
Annex B (informative):
Additional Information
Note: The following use cases are currently not in the scope of 3GPP Generic User Profile Stage 1 but they are still considered to be useful information (e.g. for future work) and therefore included in this Annex.
1. Setting up a Subscription for a new customer
- Precondition
- A person has just purchased a new device, and requires a new subscription to be initiated in the shop.
- Actions
- The user preferences for services are established.
- Information about the terminal capabilities are received from the UE.
- User Profile content is created for the Subscriber, and downloaded over the air, via local link or similar
- Post-condition
- The user can leave the shop. Her phone/device is ready to use. Basic settings needed to start and run initial applications ready.
2. Initial Service Configuration (Bootstrap)
- Precondition
- No settings made, user with a subscription
- Actions
- Settings, partly based on user profile downloaded over the air, via local link or similar
- The download initiated by the value added service provider, network operator, 3rd party or user
- User Data
- Setting received could include basic connectivity configuration parameters and the user’s security policy
- Post-condition
- The user’s phone/device ready to use. Basic settings needed to start and run initial applications ready
3. Backup/Restore of User Profile Components stored in the UE
- Precondition
- Backup
- The phone is configured, all the user preferences are set.
- The settings include user profile parameters such as generic parameters, service personalisation parameters, user’s security policy and other user preferences
- Restore
- The phone’s initial configuration enables download of configuration and user data at least via local link.
- A backup of phone configuration and user preferences is available in the network.
- Actions
- The user wishes to backup or restore the current version, or parts of the current user profile to the network, or to another UE.
- The backup/restore is performed via local link or remotely towards the network
- The backup/restore can be initiated by the user, the value added service provider, 3rd parties or the network operator
- User Profile Storage
- Secure area of the (U)SIM or ME or retained in the network by the value added service provider. User private data is only stored in the network with the user permission.
4. Content Negotiation
- Precondition
- The user has set her preferences in the UE
- Terminal type capability information is stored in ”internet”
- Actions
- The user initiates request for content. The request contains:
- User preference fetched from the UP
- Reference to the capability information is stored in ”internet”
- Deviating capability information
- Returned content selected or tailored according to User preferences and capability information
5. Terminal Management – Manual Helpdesk
- Precondition
- A user is complaining because her pocket web browser does not work. He calls the helpdesk
- Actions
- The UE capabilities are established by the helpdesk person
- A helpdesk person at an operator, value added service provider or enterprise verifies that the correct operating parameters are set on the device of a complaining user
- Post-condition
- The user’s is happy. The pocket web browser is running correctly
6. Terminal Management – Automated Self Fixing
- Precondition
- A software agent on the user’s device identifies an error.
- Actions
- It contacts the helpdesk software entity to fix the problem.
- The UE capabilities are established by the automated self-fixing solution.
- The self-fixing solution correctly diagnoses the error and provisions a bug fix.
- Post-condition
- The user’s device software executes correctly (and is happy)
7. Automatic Access Selection based on preferred list
- Precondition
- The UE shall be able to support automatic access technologies selection (i.e. without user intervention).
- The user has set her preferences in the UE and enabled automatic access technologies selection.
- A list of preferred access technologies capabilities information is stored in ”internet”
- The access technologies are authorized.
- Actions
- The user equipment initiates request for selected access technology. The request contains:
- User preferences fetched from the UP
- Reference to the access technology capabilities information is stored in ”internet”
- The preferred access technology is selected.
- Post-condition
- The preferred access technology is selected based on the order of precedence defined in a list of access technologies on the UE. The switch to a less preferred access technology, in case the most preferred is not available, takes place without user intervention.
8. Multiple Access Technology Negotiation
- Precondition
- The user has set her preferences in the UE and enabled access selection.
- Terminal type capability information is stored in ”internet”
- The access technologies are authorized
- The user has access and connection with one ongoing application
- Actions
- The (Multi-mode) terminal initiates request for another access technologies.
- The terminal chooses the most appropriate access form based on the UP and/or the sessions in progress demand of service quality.
- Returned access form selected according to User preferences and capability information.
- Post-condition
- Change of access technology without interrupting any session(s) to/from that host (context transfer).
- The old access connection end.
- The user and the terminal are connected via the new access (i.e. WLAN) with the same user identity, without having to re-authenticate.
Annex C (informative):
Bibliography
The following material, though not specifically referenced in the body of the present document (or not publicly available), gives supporting information.
3GPP TS 21.133: "3G Security; Security Threats and Requirements".
3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 1; Service description – Stage 1".
3GPP TR 22.121: "The Virtual Home Environment".
Annex D (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
SP-19 |
SP-030036 |
22.240 |
Rel-6 |
Approved at SA #19 |
2.0.0 |
6.0.0 |
|||||
|
SP-21 |
SP-030469 |
S1-030965 |
22.240 |
001 |
Rel-6 |
F |
Clarifications for section 7 of 22.240 |
6.0.0 |
6.1.0 |
GUP |
|
|
SP-22 |
SP-030707 |
S1-031256 |
22.240 |
002 |
– |
Rel-6 |
F |
Clarifications on general service requirements and data description requirements |
6.1.0 |
6.2.0 |
GUP |
|
SP-22 |
SP-030707 |
S1-031257 |
22.240 |
003 |
– |
Rel-6 |
F |
Clarifications GUP data access and administration |
6.1.0 |
6.2.0 |
GUP |
|
SP-22 |
SP-030707 |
S1-031258 |
22.240 |
004 |
– |
Rel-6 |
F |
Clarifications on GUP synchronisation |
6.1.0 |
6.2.0 |
GUP |
|
SP-23 |
SP-040095 |
S1-040202 |
22.240 |
005 |
– |
Rel-6 |
F |
GUP UE Requirements |
6.2.0 |
6.3.0 |
GUP |
|
SP-25 |
SP-040507 |
S1-040683 |
22.240 |
006 |
– |
Rel-6 |
F |
GUP, UE requirements corrections |
6.3.0 |
6.4.0 |
GUP |
|
SP-26 |
SP-040730 |
S1-040989 |
22.240 |
007 |
– |
Rel-6 |
F |
Removal of erroneous use cases |
6.4.0 |
6.5.0 |
GUP |
|
SP-42 |
Rel-7 |
Upgraded to Rel-7 without technical change. |
6.5.0 |
7.0.0 |
|||||||
|
SP-42 |
Rel-7 |
Upgraded to Rel-8 without technical change. |
7.0.0 |
8.0.0 |
|||||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
SP-49 |
SP-100575 |
S1-102054 |
22.240 |
0008 |
– |
Rel-9 |
D |
Removal of references to 3GPP OSA |
9.0.0 |
9.1.0 |
TEI9 |
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.1.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
SP-62 |
SP-130592 |
S1-135289 |
22.240 |
0009 |
1 |
Rel-11 |
F |
Correction of external references |
11.0.0 |
11.1.0 |
TEI11 |
|
2014-10 |
Updated to Rel-12 by MCC |
11.1.0 |
12.0.0 |
||||||||
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2020-01 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|