EN/FAD 109 0015 PU SCSA _PA5_1 Service Network, OSA, Parlay, Michel HoudeDr.ir. Ard-Jan Moerdijk...

_PA5_ 1

EN

/FA

D 1

09 0

015

PU SCSA

Service Network,Service Network,OSA, Parlay, OSA, Parlay,

Service Network,Service Network,OSA, Parlay, OSA, Parlay,

Michel Houde

Dr.ir. Ard-Jan MoerdijkStrategic Product and System ManagementPU-Service Capability Servers and Applications

Ericsson EuroLab Netherlands [email protected]

TSG-S 2001.01.___.___

TSG-N/TR45.2.___ 2001.01.___.___

_PA5_ 2 PU SCSAA-J Moerdijk, M. Houde

Copyright statement

c 2001 Telefonaktiebolaget LM Ericsson. The information contained in this contribution is provided for the sole purpose of promoting discussion within the Technical Specifcation Groups of TIA/3GPP2 and is not binding on Ericsson. Ericsson. reserves the right to add to, amend or withdraw the statements contained herein.

The contributor grants a free, irrevocable license to TIA/3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of TIA/3GPP2 publications; tocopyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner's standards publication. The contributor must also be willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions, as appropriate.


Agenda• Service Network• Open Service Access• OSA’s usage in 3GPP2• Standardization

• OSA application example


3rd generation network

• Need for speed: higher bit rates• (access to) Packet switched technology• Separation of

– connectivity– control– service

Enabling (portable) multi-media services /applications with reduced Time To Market


Services/Applicationslayer

Control layer

Connectivity layer

Layered network architecture principles in 3G

Network specific Call control Session management Mobility management

User data handling Transport Switching Routing User Data

Co

re n

et w

ork

Ser

vice

net

wo

rk

Applications

OPEN SERVICE

ACCESS

Defining the open interfaces Defining the open interfaces

towards applications to access towards applications to access

core network functionalitiescore network functionalities

APIs

WIN (ANSI-41)CAMEL

SIP


FutureMulti-service network

Access, Transport & Switching Networks

TodaySingle-service networks

Services

Cel

lula

r M

obile

Converged service infrastructureConverged service infrastructure

Connectivity/Connectivity/Backbone NetworkBackbone Network

Service Network

Access NetworksMGWMGWMGWMGW

MGWMGW MGWMGW

S

S S

SD

ata/

IP N

etw

orks

PLM

N (

AN

SI4

1)

PS

TN

Cel

lula

r M

obile

CA

TV

ContentContent


OSA: collection of APIs for access to core network functionality

OSA further implies:• Combinations:

– Applications by combining Network capabilities– Applications combine network capabilities with data not available in network.

• Opening up of networks for application development– technology: Java, CORBA, COM

– standards: Open APIs for support of innovative 3rd party service provisioning

• Application convergence (with the right Abstraction)– fixed, mobile, IP: OSA is beyond standards committees (i.e., 3GPP2, UMTS)– public / enterprise domain

• Backwards compatibility– Allows to generalize PLMN applications (i.e., features) logic, and reuse in the

3G context

Service Network enabler:OSA


Open Service Access: Concept

framework Loc . information Call control

AAA SCM

Locationserver

Servers(SIP)

Network Capability Gateway

Interface class

OSA interface

Application

Application server

ANSI 41

NB:The Network Capability Gateway (NCG; 3GPP: Service Capability Server) is a logical entity. It can then either be implemented as a standalone functionality, or the needed functional subset can be collocated with a network entity.


Providing the API implementations: Service

Capability Servers• Raise the abstraction layer

• Hide network specific

protocols

• Protect core network

• Act as proxies

Examples:• Call control (used for “traditional” + IP)• User interaction• User status / User location• Multi-media (IP)

• Conferencing•Terminal Capability•QoS management (i.e. policy)

•Content based charging (Content provider)


Providing the infrastructure: OSA application Framework

• Framework provides controlled access to Service Capabilities

– authentication of applications (possibly from different domains)

– authorize access to one or more Service Capabilities

• Framework enables incorporation of new Service Capabilities

– enables NCGs (SCSs) from different vendors

– enables to include non-standardized capabilities, and make them available for (some) applications


OSA’s usage in 3GPP2; Figure 3.1.4b Multimedia SIP Services Control

Plane

TrunkS igna lingG ateway

M ediaG ateway

M ediaR esourceFunction

C oreQ uality ofService

M anager

R oam ingS igna lingG ateway

S essionC ontro l

M anager

M obile IPH om eA gent

A A A

9

8

13

15 16 17

2123

24

28

47

33 34

3837

M ediaG atewayC ontro l

Function

P S TN

2620

30

22

39

S erviceA pp lica tion

45

3 4 6

7

2 5

44

48

P ositionS erver

12

M A PTIA /E IA -41

G S M

B orderR outer

46

29

40

27

PositionD eterm in ing

Entity

18

A dvertis ingA gent

25

M obileS ta tion

IPN etwork

1

cdm a2000 A ccess N e tw ork

M M

B TS

36

43

41

32

A ccessG a tew ay

F A /A ttendan t

31

35

N etworkC apab ilityG ateway

Subscrip tionQ uality ofService

M anager 141011

Legacy M SD om ainS upport

B S C /R N C+ P C F

Other Access Networks

D atabases

EIR . . .PolicyRules

N etw orkDSI Subscription

Profile

19

42



Plane


M ediaG ateway



M anager


S essionC ontro l

M anager


A A A

9

8

13

15 16 17

2123

24

28

47

33 34

3837


Function

P S TN

2620

30

22

39


45

3 4 6

7

2 5

44

48

P ositionS erver

12

M A PTIA /E IA -41

G S M

B orderR outer

46

29

40

27


Entity

18

A dvertis ingA gent

25

M obileS ta tion

IPN etwork

1


M M

B TS

36

43

41

32

A ccessG a tew ay

F A /A ttendan t

31

35



M anager 141011


B S C /R N C+ P C F


D atabases



Profile

19

42


OSA’s usage in 3GPP2

8b

T hird PartyService

Applications

N etworkC apabilityG ateway

H om eService

Applications

LocalService

Applications

8a 8c

SessionC ontro l

M anager

12

Figure 3.1.4a Multimedia Control Plane



34

25

45

62 5

48

B orderR outer

46

40

M obileS ta tion

a b c d e

39


f

47

27


31

35

P S T N

IPN etwork

14

M A PTIA /E IA -41

G S M

D atabases

M M

B TS

A ccessG atew ay

F A /A ttendan t

Legacy M S D om ain S upport

H LR S C P



T runkS igna lingG ateway


N etw orkSubscrption

ProfileDSI

M ediaG ateway

(inc ludes IW F)

M S CS erver

B S C /R N C+ P C F

Figure 3.4 Legacy MS Domain Support Contro l and Bearer View



34

25

45

62 5

48

BorderRouter

46

40

MobileStation

a b c d e

39

ServiceApplication

f

47

27

cdma2000 Access Network

31

35

PSTN

IPNetwork

14

MAPTIA/EIA-41

GSM

Databases

MM

BTS

AccessGateway

FA /Attendant

Legacy MS Domain Support

HLR SCP


RoamingSignalingGateway

TrunkSignalingGateway


NetworkSubscrption

ProfileDSI

MediaGateway

(includes IWF)

MSCServer

BSC/RNC+ PCF



a


• Parlay: – closed community, initiated by British Telecom. Now open.

– Goal: define API’s that provide enterprises access to network information and allow them to control a range of network capabilities.

• ETSI SPAN12 (formerly SPAN3):– initiators of CSx, mostly for landline

• JAIN– Service Logic Execution Environment: defines a similar concept to

OSA

• 3GPP– adopted the Virtual Home Environment concept, using Open Service

Access as a tool

OSA Standardization: Historical background


• Ongoing effort to harmonize Parlay and UMTS OSA, joint effort with ETSI SPAN12

• One API standard, one developer community!– 3GPP and ETSI joined forces on UMTS OSA, Parlay as input

– ITU refers to joint 3GPP/ETSI work on API’s

– continuous feedback and alignment with Parlay group

– ensure alignment with JAIN initiative and OMG

OSA Standardization: harmonization

_PA5_ 18

EN

/FA

D 1

09 0

015

PU SCSA

OSA application…just a sample


PLMN(ANSI41

Circuit Switched)

PSTN (Circuit Switched)

ENTERPRISE

Capability Server(s)(including interface classes)

Application

Application Server

OSA Interface providing open API’s to Applications



Recall Converged Service infrastructure, even within the Enterprise domain !

• Same application accessed from public and enterprise domainFlexibility in application ownership !

• Enterprise applications using public domain capabilities

_PA5_ 20

EN

/FA

D 1

09 0

015

PU SCSA

Leads to wide variety of OSA applications

• combinations of capabilities and data• different business roles • converged service infrastructuregives different kind of applications:

Application most likely data “owner” HEPortal Application with buddy list Network operator yes

ATM Location Application 3rd party (bank) yesMessaging application Network operator or enterprise owning data yesI nfo application Depending on info: network operator or 3rd party yes

Enterprise application 3rd party enterprise, also only subscriber no

HE:

Hom

e E

nvir

onm

ent


Location service for private subscribers

Bank services

Location services

Leisure

News



Directions

From

To ATMBankPolice

Default




PLMN(ANSI41 CS)

PSTN (CS)

User LocationSCS

Application

Application Server

OSA Interface

CC/UISCS

FW WAPGW

HE location application; interaction flow before traffic

• Application registers and authenticates towards FW

• FW checks Service Level Agreement, and starts suitable application

• UserLocationManager, returns reference to application


PLMN(ANSI41 CS)

PSTN (CS)

User LocationSCS

Application

Application Server

OSA Interface

CC/UISCS

FW WAPGW

HE location application; interaction flow during traffic

• Terminal interacts via WAP with application, selects ATM location

option

• application invokes ‘userLocationRequest’ method, gets response

• application produces suitable map (including term.caps from WAP

GW), provides this to terminal


Recommendations

1- Adopt Open Service Access concept for reference point 8



Plane


M ediaG ateway



M anager


S essionC ontro l

M anager


A A A

9

8

13

15 16 17

2123

24

28

47

33 34

3837


Function

P S TN

2620

30

22

39


45

3 4 6

7

2 5

44

48

P ositionS erver

12

M A PTIA /E IA -41

G S M

B orderR outer

46

29

40

27


Entity

18

A dvertis ingA gent

25

M obileS ta tion

IPN etwork

1


M M

B TS

36

43

41

32

A ccessG a tew ay

F A /A ttendan t

31

35



M anager 141011


B S C /R N C+ P C F


D atabases



Profile

19

42


Recommendations

2- Add Network Capability Gateway, between the Service Application(s) and the SCP (i.e., for access to legacy features)------NB:The Network Capability Gateway (NCG; 3GPP: Service Capability Server) is a logical entity. It can then either be implemented as a standalone functionality, or the needed functional subset can be collocated with a network entity.

------

3- Add a reference point between the NCG and the MSC server



34

25

45

62 5

48

BorderRouter

46

40

MobileStation

a b c d e

39

ServiceApplication

f

47

27

cdma2000 Access Network

31

35

PSTN

IPNetwork

14

MAPTIA/EIA-41

GSM

Databases

MM

BTS

AccessGateway

FA /Attendant

Legacy MS Domain Support

HLR SCP


RoamingSignalingGateway

TrunkSignalingGateway


NetworkSubscrption

ProfileDSI

MediaGateway

(includes IWF)

MSCServer

BSC/RNC+ PCF



a


Background material


Parlay API example : IparlayCall

ControlManagerPartyB : Iparlay

CallLeg : IparlayApp

Call : IparlayCallPartyA : Iparlay

CallLeg : IparlayApp

Logic

6: routeRes()

5: new()

1: new()

2: createCall()3: new()

4: routeReq()

8: routeReq()

9: new()

10: routeRes()

7: 'forward event'

11: 'forward event'


Standardization of Parlay

3GPP R99 (CN5): • Adoption of a subset of Parlay 2.1 APIs : TS 23.127 +TS

29.198– Framework: Service View– Generic Call Control– User Interaction (also for WAP push)– CAMEL based Mobility Management– Terminal Capabilities (based on WAP UAProf)– Data Session (GPRS charging)

• Informative mapping to network protocols: TR 29.998ETSI SPAN 12 (former SPAN3):• adoption of all Parlay 2.1 APIs, base for ETSI, 3GPP and ITU

Date post:	13-Dec-2015
Category:	Documents
Upload:	garey-norris
View:	214 times
Download:	0 times

EN/FAD 109 0015 PU SCSA _PA5_1 Service Network, OSA, Parlay, Michel HoudeDr.ir. Ard-Jan Moerdijk...

Documents