3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; V11.0.

0 (2012-01) Study on User Data Convergence UDC! information model Technical Report handling and provisioning" #$ample use cases %elease &&!

3GPP TR 32.901

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational Partners accept no liability for any use of this "pecification. "pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners$ Publications Offices.

%elease &&

'

3GPP T% 3'()*& +&&(*(* '*&',*&!

%eywords
UE Management, Itf-N, DMS

3GPP Postal address 3GPP support office address

6 0 R!"te #e$ %"&'!(e$ - S!)*'a +nt')!('$ Va(,!nne - -R+N.E Te(./ 033 1 92 91 12 00 -a2/ 033 1 93 6 13 16

&nternet
*tt)/44555.3g)).!6g

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
) *+,*- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& currently bein re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

.!ntent$
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 , "cope......................................................................................................................................................8 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................9
3., .bbreviations.........................................................................................................................................................9

; 2(ample "p&Ms....................................................................................................................................,+
;., 2(ample "p&M for Preferred 1urrency................................................................................................................,+ ;.*2(ample "p&M for 3ser 'ame..............................................................................................................................,+

8 .pplications.........................................................................................................................................,,
8., .pplication &nformation Models (.&M)..............................................................................................................,, 8.,.,&nformation Object 1lasses................................................................................................................................,, 8.,.,.+ General ,, 8.,.,., 3dc.""erviceProfile.....................................................................................................................................,* 8.,.,.* 3:10asic"erviceProfile................................................................................................................................,* 8.,.,.3 3:11"17"erviceProfile...............................................................................................................................,* 8.,.,.; 3dc<"""erviceProfile...................................................................................................................................,* 8.,.,.8 3dc"pecial"ervicesProfile.............................................................................................................................,* 8.,.,.= 3dc1""erviceProfile.....................................................................................................................................,* 8.,.,.> 3dc2P""erviceProfile...................................................................................................................................,* 8.,.,.9 3dcGP/""erviceProfile................................................................................................................................,* 8.,.,.? 3dc&M""erviceProfile...................................................................................................................................,* 8.,.,.,+ 3dcMMTel"erviceProfile............................................................................................................................,* 8.,.* 1"@GP/"...........................................................................................................................................................,3 8.,.*., <5/ ,3 8.,.3 2P" ,3 8.,.3., <"" ,3 8.,.; &M" ,; 8.,.;., 1"17 ,; 8.,.;.* MMTel ,; 8.* "P&M 5evel..........................................................................................................................................................,; 8.*.,Preferred 1urrency 3se 1ase.............................................................................................................................,; 8.*.,., "ettin or modification of the value of this data item....................................................................................,8 8.*.,.* "cenarios for use of the data element.............................................................................................................,8 8.*.* . e and 0irth :ate 3se 1ase............................................................................................................................,8 8.*.*., "ettin or modification of the value of this data item....................................................................................,8 8.*.*.* "cenarios for use of the . e data element....................................................................................................,8 8.*.3'ame 3se 1ase..................................................................................................................................................,= 8.*.3., &nput for 'ame...............................................................................................................................................,= 8.*.3.* "cenarios for use of the data element 'ame..................................................................................................,= 8.*.; Gender 3se 1ase...............................................................................................................................................,= 8.*.;., "ettin or modification of the value of this data item....................................................................................,= 8.*.;.* "cenarios for use of the data element.............................................................................................................,= 8.*.8 Preferred 5an ua e 3se 1ase...........................................................................................................................,= 8.*.8., "ettin or modification of the value of this data item....................................................................................,> 8.*.8.* "cenarios for use of the data element.............................................................................................................,> 8.*.= 7riend@7riends 5ist 3se 1ase............................................................................................................................,> 8.*.=., "ettin or modification of the value of this data item....................................................................................,> 8.*.=.* "cenarios for use of the data element.............................................................................................................,>

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

= /ecommendations re ardin provisionin Annex A:

uidelines and reAuirements..............................................,9

Change history.............................................................................................................19

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

-!6e5!6#
This Technical /eport has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e followin formal T"G approval. "hould the T"G modify the contents of the present document- it will be reBreleased by the T"G with an identifyin chan e of release date and an increase in version number as followsC Dersion (.y.! whereC ( the first di itC , presented to T"G for informationE * presented to T"G for approvalE 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

S&!)e

3GPP T/ **.?98 "ervice reAuirement for the 3:1 F8G describes the architecture of the 3ser :ata 1onver ence- a concept that proposes to move the user data from where it has been distributed and siloed in 'etwor# 2lements.pplications- and other networ# resources to a sin le lo ical consolidated facility here called 3ser :ata /epository (3:/) where it can be accessed- stored and mana ed in a common way. The introduction of a 3ser :ata 1onver ence of user data for networ# services and mana ement applications could si nificantly enhance the ability of 3GPP based networ#s to offer comple( and combined services. 3ser data can be decomposed and reformed by a common data model framewor# (e. . treeBli#e data model- rational data model) provided by 3:/. &n that case- user data cate ori!ed by services can be re rouped and identified by user &:- leavin no data redundancy. .lso- conver ence in data model will unify the user data access interface and its protocol- which will promote new service application development. Thereby- the capability of user data conver ence can be open to creation of dataBless applications. Methods for data protection a ainst access by unauthori!ed parties are outside the scope of this document. 3GPP T" 3*.,9, 3:1 7ramewor# for Model <andlin and Mana ement F3G and 3GPP T" *?.338 3:1E 3ser :ata /epository .ccess Protocol over the 3d interfaceE "ta e 3 F;G provide various types of information and data models associated with the architecture of 3:1. These include the 1ommon 0aseline &nformation Model (10&M) (see 3GPP T" 3*.,9* F>G)- the "peciali!ed &nformation Model ("p&M)- .pplication &nformation Models (.&Ms)- .pplication :ata Models (.:Ms)- and the 1onsolidated :ata Model (1:M) of the 3ser :ata /epository (3:/). 7i ure , from 3GPP T" 3*.,9, 3:1 7ramewor# for Model <andlin and Mana ement F3G shows the operational environment of the 3:1.

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

/SS

Generate ne0 CD1

P6!7'$'!n'ng Gate5a8
-"(( Data V'e5

Ud

S)IM S)IM

Appl &

pl & Ap 0 +ie

Generate AD1 and mapping and ne0 Sp21

AP P

3'

vie 0
Ud

Consolidated Data 1odel (CD1)

P AP 3n 0 vie

APP3 3 vie0
Ud

Appl '

ne5 ne5 +IM +IM

ne0 Appl

4igure &(&" #volution of the CD1 in a UD% &n addition to the models previously mentioned- 7i ure ,., introduces the aspect of the Provisionin Gateway- which is essential for the operation of the 3:/. The Provisionin Gateway provides a sin le lo ical point for access to provisionin of user data for all services in the 3:/. The Provisionin Gateway is shown supportin an interaction with the operator$s 0""E by implication this interaction is associated with the provisionin of user subscription and service data in the 3:/ via the Provisionin Gateway. This study analy!es the pro ression of information models displayed in the above fi ure usin some specific application e(amples- in particular the applications of <""B&M" and MMTel. &t provides uidelines and preliminary reAuirements for the 0"" provisionin capabilities and information model handlin when new applications and related services are implemented in the operator$s 3:/ by doin the followin C :evelop several e(ample initial "p&Ms for discussion purposes. 2(amine what 0"" interactions with the Provisionin Gateway would be reAuired to support provisionin of user service and subscription data in the 3:/ for these "p&Ms. "tudy the relationship to the information model of 3GPP T" 3*.,>* "ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &/P &nformation "ervice F?G. :evelop understandin of 10&MBderived entities of .pplication &nformation Models (.&M) for <""B&M" and MMTel from application data elements available in 3GPP T" *?.3=; &M" .pplication "erver service data descriptions for ." interoperability F,,G- 3GPP T" *3.++9 Or ani!ation of subscriber data F,*G- and other relevant specifications. :iscuss the inte ration and consolidation of these .&M entities with the e(ample initial "p&Ms above.

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

2valuate the potential chan es to the 0"" provisionin interactions for the implementation of <""B&M" and MMTel applications in the 3:/ and implications concernin the information model of 3GPP T" 3*.,>* "ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &/P &nformation "ervice F?G.

This study does not derive findin s concernin the 3d reference point- the subject of 3GPP T/ *3.9;8 "tudy on 3:1 2volution F,+G.

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

Refe6en&e$
/eferences are either specific (identified by date of publication and@or edition number or version number) or nonBspecific. 7or a specific reference- subseAuent revisions do not apply. 7or a nonBspecific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a nonBspecific reference implicitly refers to the latest version of that document in the same Release as the present document. F,G F*G F3G F;G F8G F=G F>G F9G F?G F,+G F,,G F,*G 3GPP T/ *,.?+8C HDocabulary for 3GPP "pecificationsH. 3GPP T" *3.338C H3ser :ata 1onver ence (3:1)E Technical reali!ation and information flowsE "ta e *H. 3GPP T" 3*.,9,C H3ser :ata 1onver ence (3:1)E 7ramewor# for Model <andlin and Mana ementH. 3GPP T" *?.338C H3ser :ata 1onver ence (3:1)E 3ser :ata /epository .ccess Protocol over the 3d interfaceE "ta e 3H. 3GPP T/ **.?98C H"ervice reAuirement for the 3ser :ata 1onver ence (3:1)H. 3GPP T" **.,+,C H"ervice aspectsE "ervice principlesH. 3GPP T" 3*.,9*C H3ser :ata 1onver enceE 1ommon 0aseline &nformation ModelH. 3GPP T/ 3*.9+9C H"tudy of 1ommon Profile "tora e (1P") 7ramewor# of 3ser :ata for networ# services and mana ementH. 3GPP T" 3*.,>*C H"ubscription Mana ement ("uM) 'etwor# /esource Model ('/M) &nte ration /eference Point (&/P)C &nformation "ervice (&")H. 3GPP T/ *3.9;8C H"tudy on 3:1 2volutionH. 3GPP T" *?.3=;C H&P Multimedia "ystem (&M") .pplication "erver (.") service data descriptions for ." interoperabilityH. 3GPP T" *3.++9C HOr ani!ation of subscriber dataH.

The followin documents contain provisions which- throu h reference in this te(t- constitute provisions of the present document.

Def'n't'!n$ an# a,,6e7'at'!n$

3.1 +,,6e7'at'!n$
7or the purposes of the present document- the followin abbreviations applyC .&M .:M 0"" 10&M 1:M 1P" 72 <"" &M" &/P .pplication &nformation Model .pplication :ata Model 0usiness "upport "ystem 1ommon 0aseline &nformation Model 1onsolidated :ata Model 1ommon Profile "tora e 7ront 2nd <ome "ubscriber "erver &P Multimedia "ystem &nte ration /eference Point

3GPP

%elease &&

3GPP T% 3'()*& +&&(*(* '*&',*&!

&" 5:.P MMTel '/M /:M "p&M "uM 3:1 3:/

&nformation "ervice 5i htwei ht :irectory .ccess Protocol MultiMedia Telephony 'etwor# /esource Model /eference :ata Model "peciali!ed &nformation Model "ubscription Mana ement 3ser :ata 1onver ence 3ser :ata /espository

3GPP

%elease &&

&*

3GPP T% 3'()*& +&&(*(* '*&',*&!

E2am)(e S)IM$

1.1 E2am)(e S)IM f!6 P6efe66e# ."66en&8

. user can reAuest that any char in or pricin information be provided usin a specific currency. The method is operator specific- but the e(ample shown below is typical of what would transpire to derive the "p&M and resultin :ata Model.

C/21 information for currency selection

Appl 21 A21! 9perator currency selection process

2ntegrate A21 into Sp21 and consolidate

Speciali8ed 21 Sp21! for User Currency Preferrence 1.2 E2am)(e S)IM f!6 U$e6 Name
. user can reAuest that his@her name be made available for messa in and special services as a particular value- e. . IJane M. :oeK- or I:r. Terry L. "mith &DK. The method is operator specific- but the e(ample shown below is typical of what would transpire to derive the "p&M and resultin :ata Model.

3GPP

%elease &&

&&

3GPP T% 3'()*& +&&(*(* '*&',*&!

C/21 name information

Appl 21 A21! 9perator user name selection process

2ntegrate A21 into Sp21 and consolidate

Speciali8ed 21 Sp21! for User :ame

+))('&at'!n$
This section describes application data for all networ# domains supportin 3:1 handlin and provisionin . The domains shown below are at the .&M level includin 1"- 2P"- and &M". The AIM import from existing applications is outside the scope of the present document. This study is not an application guide.

.1 +))('&at'!n Inf!6mat'!n M!#e($ (+IM)

.&M may be imported from e(istin applications or may be enerated from information elements already e(istin in the 3:/. The import method is for further study. .n .&M should contain &O1s for B B the "ervice Profile(s) of the particular application&dentifier(s) used by the application.

and additionally- if needed- any other &O1 defined in 10&M. 2. . related 2nd :evice- if such is to be connected to one or more identifiers within the application.

.1.1 Inf!6mat'!n 9,:e&t .(a$$e$

.1.1.0 Gene6a(

The information object classes described in 8.,.,., throu h 8.,.,.,+ are meant to illustrate the use of e(ample data within the conte(t of this study document- and not meant as replacements or to supersede any &O1s in any 3GPP specifications-

3GPP

%elease &&

&'

3GPP T% 3'()*& +&&(*(* '*&',*&!

.1.1.1

U#&+SSe67'&eP6!f'(e

This is a class created only to represent some ASServiceProfile data within the context of this example . &t can be uniAue to the operator.

.1.1.2

UD.;a$'&Se67'&eP6!f'(e

This is a class created only to represent some BasicServiceProfile data within the context of this example . &t can be uniAue to the operator.

.1.1.3

UD..S.-Se67'&eP6!f'(e

This is a class created only to represent some S !ServiceProfile data within the context of this example . &t can be uniAue to the operator.

.1.1.1

U#&<SSSe67'&eP6!f'(e

This is a class created only to represent some "SSServiceProfile data within the context of this example . &t can be uniAue to the operator.

.1.1.

U#&S)e&'a(Se67'&e$P6!f'(e

This is a class created only to represent some SpecialServicesProfile data within the context of this example . &t can be uniAue to the operator.

.1.1.6

U#&.SSe67'&eP6!f'(e

This object class is provided in 3GPP T" 3*.,9*- and represents the part of the UdcServiceProfile that contains data related to 1ircuitB"witched services. .n e(ample of further speciali!ation of this object class- includin attributesis provided in 3GPP T" 3*.,9,.

.1.1.3

U#&EPSSe67'&eP6!f'(e

This object class represents the part of the UdcServiceProfile that contains data related to the 2volved Pac#et "ystem services. .n e(ample of further speciali!ation of this object class- includin attributes- is provided in 3GPP T" 3*.,9,.

.1.1.=

U#&GPRSSe67'&eP6!f'(e

This object class is provided in 3GPP T" 3*.,9*- and represents the part of the UdcServiceProfile that contains data related to Pac#etB"witched services. .n e(ample of further speciali!ation of this object class- includin attributesis provided in 3GPP T" 3*.,9,.

.1.1.9

U#&IMSSe67'&eP6!f'(e

This object class is provided in 3GPP T" 3*.,9*- and represents the part of the UdcServiceProfile that contains data related to &M" services. .n e(ample of further speciali!ation of this object class- includin attributes- is provided in 3GPP T" 3*.,9,.

.1.1.10

U#&MMTe(Se67'&eP6!f'(e

This is a class created only to represent some MMTel"erviceProfile data within the conte(t of this e(ample. &t can be uniAue to the operator. The use of MMTel data is typically transparent to applications and is usually part of the .""erviceProfile. &t is shown here as one e(ample of how the data is modeled.

3GPP

%elease &&

&3

3GPP T% 3'()*& +&&(*(* '*&',*&!

.1.2 .S4GPRS
.1.2.1 <%R
>>Inf!6mat'!n9,:e&t.(a$$?? U#&.$Se67'&eP6!f'(e >>Inf!6mat'!n9,:e&t.(a$$?? U#&G)6$Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&;a$'&Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&S)e&'a( Se67'&e$P6!f'(e

4igure .(&,&" Consolidation of data in the application for CS;GP%S,<3% 2ditor$s noteC This dia ram is an e(ample and is 77".

.1.3 EPS
.1.3.1 <SS
>>Inf!6mat'!n9,:e&t.(a$$?? U#&EPSSe67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&;a$'&Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&S)e&'a(Se67'&e$P6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&<SSSe67'&eP6!f'(e

4igure .(&,'" Consolidation of data in the application for #PS,<SS 2ditor$s noteC This dia ram is an e(ample and is 77".

3GPP

%elease &&

&-

3GPP T% 3'()*& +&&(*(* '*&',*&!

.1.1 IMS
.1.1.1 .S.>>Inf!6mat'!n9,:e&t.(a$$?? IIMSSe67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&;a$'&Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&S)e&'a( Se67'&e$P6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&.S.-Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&+SSe67'&eP6!f'(e

4igure .(&,3" Consolidation of data in the application for 21S CSC4 2ditor$s noteC This dia ram is an e(ample and is 77".

.1.1.2

MMTe(
>>Inf!6mat'!n9,:e&t.(a$$?? IIMSSe67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&;a$'&Se67'&eP6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&S)e&'a( Se67'&e$P6!f'(e

>>Inf!6mat'!n9,:e&t.(a$$?? U#&MMTe(Se67'&eP6!f'(e $

>>Inf!6mat'!n9,:e&t.(a$$?? U#&+SSe67'&eP6!f'(e

4igure .(&,-" Consolidation of data in the application for 21S 11Tel 2ditor$s noteC This dia ram is an e(ample and is 77".

.2
.2.1

SPIM %e7e(
P6efe66e# ."66en&8 U$e .a$e

2(pression of currency information to the subscriber in a particular currency may be supported by settin the optional H1urrency PreferenceH subscription data element. The values for this data element may be any national currency (eurosJapanese yen- 3.". dollars- etc.)C

3GPP

%elease &&

&.

3GPP T% 3'()*& +&&(*(* '*&',*&!

.2.1.1

Sett'ng !6 m!#'f'&at'!n !f t*e 7a("e !f t*'$ #ata 'tem

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interface that the operator provides- or throu h interaction with an operator customer representative.

.2.1.2

S&ena6'!$ f!6 "$e !f t*e #ata e(ement

0elow are e(amples of scenarios in which different applications may use the same 1urrency Preference data element to beneficially improve the subscriberMs service e(perience. One type of subscriber case where use of this data element would be most meanin ful would be a when a person has travelled to another country (either as a tourist or on business) and starts a subscription with an operator in that visited country. a) . subscriber calls a freephone number to automated routine of .cme .irlines to et a tic#et price for a certain itinerary. This Nprompt and collect menuBdriven application is runnin on an ." in the networ#. .t the point where the application is about ready to provide the price Auote- &t chec#s the subscriberMs profile for the Preferred 1urrency settin - and provides the Auote in that currency. b) . subscriber with a smartphone is at the operatorMs smartphone Happ storeH. The app store chec#s the subscriberMs subscriberMs profile for the Preferred 1urrency settin . .s the subscriber browses apps- the app prices are stated in the preferred currency. c) The subscriber ma#es an international call and invo#es the operatorMs .dvice of 1har e supplementary service to be told the price of the call when it ends. .nd perhaps may be provided the cumulative priceBsoBfar updates at periodic intervals durin the call. The .dvice of 1har e application chec#s the subscriberMs profile for a preferred currency- and indicates the advice of char e information to the subscriber in that currency.

.2.2

+ge an# ;'6t* Date U$e .a$e

2(pression of a e and birth date to the subscriber may be supported by settin the optional H. e PreferenceH subscription data element. The values for this data element may be a e in years or birth dateC

.2.2.1

Sett'ng !6 m!#'f'&at'!n !f t*e 7a("e !f t*'$ #ata 'tem

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interface that the operator provides- or throu h interaction with an operator customer representative. The operator has to responsibility to verify the a e of the subscriber to ensure a e appropriate information is conveyed.

.2.2.2

S&ena6'!$ f!6 "$e !f t*e +ge #ata e(ement

0elow are e(amples of scenarios in which different applications may use the same . e data element to beneficially improve the subscriberMs service e(perience- perhaps is a criteria for decidin if service fulfilment is to be allowedeither accordin to operator policy or national re ulations- or perhaps as a way of tar etin specific advertisin to the subscriber. a) . subscriber calls a freephone number for .cme airlines- e. .- for travel information or to ma#e a reservation. There is a Aueue. The .cme airlines application chec#s the subscriber profile for a e information and- if setselects the type of music or advertisin or both that are played to that specific subscriber while in Aueue. b) . subscriber with a smartphone is browsin the operatorMs app store. 1ertain apps with inappropriate themes for children are not to be displayed to subscribers@users under the a e of ,9- due to operator policy or federal re ulation. The app store chec#s the subscriber profile and uses the . e data element to determine whether the under ,9. ('oteC in order to purchase- this may still be followed up with a step where the users must confirm that they are over ,9.) . subscriber calls a freephone number for a H7ind Me . /estaurantH application and as#s for recommendations for a ood &talian restaurant in the local area. &n this particular case there are lots of such restaurants- and so the application needs to apply some criteria determinin just what recommendations to ma#e available to the subscriber. "tatiscally- the application #nows that some of the restaurants are more popular with the youn er crowd and others with the older crowd. The application chec#s the subscriber profile for the . e value to help determine the specfiic restaurant

3GPP

%elease &&

&5

3GPP T% 3'()*& +&&(*(* '*&',*&!

su estions to the subscriber. ('oteC the application could certainly use other criteria as well.) &t may also use the . e value to select the appropriate coupon enticement to offer to the subscriber (free appeti!er- free drin#- or free dessert).

.2.3

Name U$e .a$e

The name of the subscriber may be supported by settin the optional H'ameH subscription data element.

.2.3.1

In)"t f!6 Name

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interfance that the operator provides- or throu h interaction with an operator customer representative.

.2.3.2

S&ena6'!$ f!6 "$e !f t*e #ata e(ement Name

0elow are e(amples of scenarios in which different applications may use the 'ame data element to beneficially improve the subscriberMs service e(perience. One type of subscriber case where use of this data element would be most meanin ful would be a when a person wishes to have his or her name be #nown for personali!ed notices and offerin s. a) . subscriber receives a personali!ed reetin - and is as#ed that name be maded available for friends list- or to a vendor for product offerin s. b) . subscriber with a smartphone is at the operatorMs smartphone Happ storeH. The Happ storeH chec#s the subscriberMs subscriberMs profile for the 'ame settin . .s the subscriber browses apps- the app prices are stated to the subscriber in their name. c) The subscriber ma#es a a call and their name is presented to the called party.

.2.1 Gen#e6 U$e .a$e

The ender of the subscriber may be supported by settin the optional HGenderH subscription data element.

.2.1.1

Sett'ng !6 m!#'f'&at'!n !f t*e 7a("e !f t*'$ #ata 'tem

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interfance that the operator provides- or throu h interaction with an operator customer representative.

.2.1.2

S&ena6'!$ f!6 "$e !f t*e #ata e(ement

0elow are e(amples of scenarios in which different applications may use the Gender data element to beneficially improve the subscriberMs service e(perience. One type of subscriber case where use of this data element would be most meanin ful would be a when a subscriber$s ender reAuired for specific services. a) . subscriber calls a merchant to et a price for a certain item. This Nprompt and collect menuBdriven application is runnin on an ." in the networ#. .t the point where the application is about ready to provide the price Auote&t chec#s the subscriberMs profile for the Gender settin - and provides the information as#ed for and offers some ender related su estions.. b) . subscriber with a smartphone wishes to be networ#ed into a ender related social action roup- or a ender related roup is see#in membership and solicits the subscriber to join its or ani!ation. c) The subscriber ma#es a call and as#s for assiistance. The responders can tar et their actions based on appropriate ender.

.2. P6efe66e# %ang"age U$e .a$e

2(pression of lan ua e information to the subscriber in a particular lan ua e may be supported by settin the optional H5an ua e PreferenceH subscription data element. The values for this data element may be any lan ua e supported by the networ#.

3GPP

%elease &&

&6

3GPP T% 3'()*& +&&(*(* '*&',*&!

.2. .1

Sett'ng !6 m!#'f'&at'!n !f t*e 7a("e !f t*'$ #ata 'tem

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interfance that the operator provides- or throu h interaction with an operator customer representative.

.2. .2

S&ena6'!$ f!6 "$e !f t*e #ata e(ement

0elow are e(amples of scenarios in which different applications may use the same 5an ua e Preference data element to beneficially improve the subscriberMs service e(perience. One type of subscriber case where use of this data element would be most meanin ful would be a when a person has travelled to another country (either as a tourist or on business) and starts a subscription with an operator in that visited country. a) . subscriber calls a freephone number to automated routine of .cme .irlines to et information for a certain itinerary. This Nprompt and collect menuBdriven application is runnin on an ." in the networ#. .t the point where the application is about ready to provide the itinerary- &t chec#s the subscriberMs profile for the Preferred 5an au e settin - and provides the information in that lan ua e. b) . subscriber with a smartphone is at the operatorMs smartphone Happ storeH. The Happ storeHchec#s the subscriberMs subscriberMs profile for the Preferred 5an ua e settin . .s the subscriber browses apps- the app items are stated in the preferred lan ua e. c) The subscriber ma#es an international call and invo#es the operatorMs .dvice of 1har e supplementary service to be told the price of the call when it ends. .nd perhaps may be provided the cumulative priceBsoBfar updates at periodic intervals durin the call. The .dvice of 1har e application chec#s the subscriberMs profile for a preferred lan au e- and indicates the advice of char e information to the subscriber in that lan au e.

.2.6 -6'en#4-6'en#$ %'$t U$e .a$e

The list of friends of the subscriber may be supported by settin the optional H7riends 5istH subscription data element. The values for this data element may be a list representin a friends call roup$ or individual friend call numbers.

.2.6.1

Sett'ng !6 m!#'f'&at'!n !f t*e 7a("e !f t*'$ #ata 'tem

The subscriber may be able to chan e the value of this data element throu h an appropriate procedure at any time- e. .a subscription profile web interfance that the operator provides- or throu h interaction with an operator customer representative.

.2.6.2

S&ena6'!$ f!6 "$e !f t*e #ata e(ement

0elow are e(amples of scenarios in which different applications may use the 7riends identifier data element to beneficially improve the subscriberMs service e(perience. One type of subscriber case where use of this data element would be most meanin ful would be a when a person wishes to contact an individual friend or roup of friends. a) . subscriber wants to notify a friend or roup of friends of a particular event.. This Nnotification$ menuBdriven application is runnin on an ." in the networ#. .t the point where the application is about to process the serviceit determines that a friends list e(ist- and will forward the notification to all members in that list. b) .n operator has just provided a specific application service to the subscriber who has a friends list. The 7riends 5ist data elements are then used to notify all members in that list of the service. "ome e(amples are The subscriber has just landed on an internation al fli ht and re isters his mobile with the local operator. The operator determines the presence of the 7riends 5ist application and chec#s which type of subscribed notifications can be applied. The ." then notifies the friend or friends of the arrival.and local re istration. The subscriber has a specific event and wants friends to be automatically notified. The friends ." will send the notice to all members in the list.

3GPP

%elease &&

&7

3GPP T% 3'()*& +&&(*(* '*&',*&!

Re&!mmen#at'!n$ 6ega6#'ng )6!7'$'!n'ng g"'#e('ne$ an# 6e@"'6ement$

The result of this study is for further consideration and is a uide for use by operators in the application of 3:1 for speciali!ed services.

3GPP

%elease &&

&)

3GPP T% 3'()*& +&&(*(* '*&',*&!

+nne2 +/ .*ange *'$t!68

Change history
Date 2011-11 2012-12 TSG TSG Doc( = SP- 1 SP-110693 --C% --%ev Su>ject;Comment --P6e$entat'!n t! S+ f!6 'nf!6mat'!n an# a))6!7a( P",('&at'!n Cat 9ld ----1.0. 0 :e0 1.0.0 11.0.0

3GPP