User Profile Description Bo I Johanssonecs ericsson se

  • Slides: 15
Download presentation
User Profile Description Bo. I. Johansson@ecs. ericsson. se Olga. Tome@ecs. ericsson. se Gunilla. Bratt@ecs.

User Profile Description Bo. I. [email protected] ericsson. se Olga. [email protected] ericsson. se Gunilla. [email protected] ericsson. se 2001 -05 -13 Ericsson T 2#13, User Profile Description 1

User Profile Description • Background • Working assumptions • Proposal Data Description Principles 2001

User Profile Description • Background • Working assumptions • Proposal Data Description Principles 2001 -05 -13 Ericsson T 2#13, User Profile Description 2

User Profile, Terminal View ”MEx. E” Server UP Capability Negotiation Profile Update Phone 2001

User Profile, Terminal View ”MEx. E” Server UP Capability Negotiation Profile Update Phone 2001 -05 -13 Ericsson Term. Manag. UP Server Terminal Management UP Back Up Restore API VHE UP VHE Sync A P I OSA VHE Sync Application SIM? ? UP Application Phone UP Moved SIM UP T 2#13, User Profile Description 3

User Profile, Network View HSS User Profile Personalisation Data in terminal Subscription Homepage User’s

User Profile, Network View HSS User Profile Personalisation Data in terminal Subscription Homepage User’s Homepage Wireless Network Personalisation Data in USIM Service Related Data 2001 -05 -13 Ericsson HE-VASP T 2#13, User Profile Description VASP 4

Same Data, Different Usages To avoid multiple descriptions In standardisation • Describe the data

Same Data, Different Usages To avoid multiple descriptions In standardisation • Describe the data once • Try to used Generic Mapping to Formats – – Transport format Protocol Application programming Interface, API. . . 2001 -05 -13 Ericsson T 2#13, User Profile Description 5

Describe once, Use many Capability Negotiation Terminal Management Mapping Data Description 2001 -05 -13

Describe once, Use many Capability Negotiation Terminal Management Mapping Data Description 2001 -05 -13 Ericsson Mapping Subscription Management Mapping Terminal VHE sync Mapping Data T 2#13, User Profile Description 6

Working assumptions our current!! 2001 -05 -13 Ericsson T 2#13, User Profile Description 7

Working assumptions our current!! 2001 -05 -13 Ericsson T 2#13, User Profile Description 7

Data Description Requirements (1) • Re-usable description components – Equal/Similar parts where possible –

Data Description Requirements (1) • Re-usable description components – Equal/Similar parts where possible – Distributed responsibility between std. bodies – Some description components standardised some late defined • Computer parseable Data Description • Define a Default Transport Format • Backward compatibly – Avoid to redo all existing data descriptions! • Extendable – Start with Terminal Management data, later also other data 2001 -05 -13 Ericsson T 2#13, User Profile Description 8

Data Description Requirements (2) • Expressiveness Balance – Expressiveness to describe data – Requirement

Data Description Requirements (2) • Expressiveness Balance – Expressiveness to describe data – Requirement on Terminal Management complexity • Fulfil Requirements from – Use Cases – Security 2001 -05 -13 Ericsson T 2#13, User Profile Description 9

Working Assumption (1) • One User Profile Is composed of User Profile Components •

Working Assumption (1) • One User Profile Is composed of User Profile Components • Each User Profile Component, UPC, has – – Identification Semantic (i. e. meaning of the UPC) Schema (i. e. vocabulary, UPC data type) Values • An User Profile Description consists of – List of User Profile Components – Set of schemas that defines the syntax and semantic of all UPC types 2001 -05 -13 Ericsson T 2#13, User Profile Description 10

Working Assumption (2) The rules how to create User Profile Descriptions are called a

Working Assumption (2) The rules how to create User Profile Descriptions are called a Data Description Framework • The Data Description Framework is standardised • Some of the User Profile Components are standardised • Use XML where suitable 2001 -05 -13 Ericsson T 2#13, User Profile Description 11

Data Description Principles 2001 -05 -13 Ericsson T 2#13, User Profile Description 12

Data Description Principles 2001 -05 -13 Ericsson T 2#13, User Profile Description 12

”Meta” Levels Data Description Framework Defines how to do the data description Data Description

”Meta” Levels Data Description Framework Defines how to do the data description Data Description Describes the data Data stored and accessed in a device 2001 -05 -13 Ericsson T 2#13, User Profile Description 13

Example: Device Management usage Data Description Framework XML-document Structure Data Description Device Type Content

Example: Device Management usage Data Description Framework XML-document Structure Data Description Device Type Content Semantic Structure Device Configuration Parameter values Content Managed device Management system ie ”Sync. ML” or MEx. E 2001 -05 -13 Ericsson T 2#13, User Profile Description 14

<Settings> <Audio. Settings> <Ring. Volume>2</Ring. Volume> <Increasing. Ring>ON</Increasing. Ring> <Vibrating. Alert>ON</Vibrating. Alert>. . .

2 ON ON. . . Anders 13 . . . . . 2001 -05 -13 Ericsson T 2#13, User Profile Description 15