Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.198  Word version:  9.0.0

Top   Top   None   None   Next
0…   5…

 

0  IntroductionWord‑p. 5

The Open Service Access (OSA) defines an architecture that enables service application developers to make use of network functionality through open standardized interface, i.e. the OSA APIs and Parlay X Web Services. The network functionality is describes as Service Capability Features (SCFs) or Services. The OSA Framework is a general component in support of Services (Service Capabilities) and Applications. The concepts and the functional architecture for the OSA are contained in the present document. The requirements for OSA are contained in TS 22.127.
The present document is part of a TS-family as identified below:
22.127:
"Service Requirement for the Open Services Access (OSA); Stage 1".
23.198:
"Open Service Access (OSA); Stage 2".
Stage 3 Technical Specifications (TSs):
29.198-01:
"OSA API; Part 1: Overview".
29.198-02:
"OSA API; Part 2: Common data".
29.198-03:
"OSA API; Part 3: Framework".
29.198-04-1:
"OSA API; Part 4: Call control; Subpart 1: Common call control data definitions".
29.198-04-2:
"OSA API; Part 4: Call control; Subpart 2: Generic call control data SCF".
29.198-04-3:
"OSA API; Part 4: Call control; Subpart 3: Multi-party call control data SCF".
29.198-04-4:
"OSA API; Part 4: Call control; Subpart 4: Multimedia call control SCF".
29.198-04-5:
"OSA API; Part 4: Call control; Subpart 5: Conference call control SCF".
29.198-05:
"OSA API; Part 5: Generic user interaction".
29.198-06:
"OSA API; Part 6: Mobility".
29.198-07:
"OSA API; Part 7: Terminal capabilities".
29.198-08:
"OSA API; Part 8: Data session control".
29.198-09:
does not exist
29.198-10:
"OSA API; Part 10: Connectivity manager SCF".
29.198-11:
"OSA API; Part 11: Account management".
29.198-12:
"OSA API; Part 12: Charging".
29.198-13:
"OSA API; Part 13: Policy management SCF".
29.198-14:
"OSA API; Part 14: Presence and Availability Management (PAM)".
29.198-15:
"OSA API; Part 15: Multi-media Messaging (MM) SCF".
29.198-16:
"OSA API; Part 16: Service Broker Service Capability Feature (SCF)".
29.199-01:
"OSA; Parlay X web services; Part 1: Common".
29.199-02:
"OSA; Parlay X web services; Part 2: Third party call".
29.199-03:
"OSA; Parlay X web services; Part 3: Call notification".
29.199-04:
"OSA; Parlay X web services; Part 4: Short messaging".
29.199-05:
"OSA; Parlay X web services; Part 5: Multimedia messaging".
29.199-06:
"OSA; Parlay X web services; Part 6: Payment".
29.199-07:
"OSA; Parlay X web services; Part 7: Account management".
29.199-08:
"OSA; Parlay X web services; Part 8: Terminal status".
29.199-09:
"OSA; Parlay X web services; Part 9: Terminal location".
29.199-10:
"OSA; Parlay X web services; Part 10: Call handling".
29.199-11:
"OSA; Parlay X web services; Part 11: Audio call".
29.199-12:
"OSA; Parlay X web services; Part 12: Multimedia conference".
29.199-13:
"OSA; Parlay X web services; Part 13: Address list management".
29.199-14:
"OSA; Parlay X web services; Part 14: Presence".
29.199-15:
"OSA; Parlay X web services; Part 15: Message Broadcast".
29.199-16:
"OSA; Parlay X web services; Part 16: Geocoding".
29.199-17:
"OSA; Parlay X web services; Part 17: Application driven Quality of Service (QoS)".
29.199-18:
"OSA; Parlay X web services; Part 18: Device management".
29.199-19:
"OSA; Parlay X web services; Part 19: Multimedia streaming control".
29.199-20:
"OSA; Parlay X web services; Part 20: Multimedia multicast session management".
29.199-21:
"OSA; Parlay X web services; Part 21: Content management".
29.199-22:
"OSA; Parlay X web services; Part 22: Policy".
Technical Reports (TRs):
29.998-01:
"OSA API Mapping for OSA; Part 1: General issues on API mapping".
29.998-04-1:
"OSA API Mapping for OSA; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping".
29.998-04-2:
"OSA API Mapping for OSA; Part 4: Call Control Service Mapping; Subpart 2: INAP".
29.998-04-3:
"OSA API Mapping for OSA; Part 4: Call Control Service Mapping; Subpart 3: MEGACO mapping".
29.998-04-4:
"OSA API Mapping for OSA; Part 4: Call Control Service Mapping; Subpart 4: Multiparty Call Control ISC".
29.998-05-1:
"OSA API Mapping for OSA; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping".
29.998-05-2:
"OSA API Mapping for OSA; Part 5: User Interaction Service Mapping; Subpart 2: INAP mapping".
29.998-05-3:
"OSA API Mapping for OSA; Part 5: User Interaction Service Mapping; Subpart 3: MEGACO mapping".
29.998-05-4:
"OSA API Mapping for OSA; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping".
29.998-06-1:
"OSA API Mapping for OSA; Part 6: User Location - User Status Service Mapping; Subpart 1: Mapping to MAP".
29.998-06-2:
"OSA API Mapping for OSA; Part 6: User Location - User Status Service Mapping; Subpart 1: Mapping to SIP".
29.998-08:
"OSA API Mapping for OSA; Part 8: Data Session Control Service Mapping to CAP".
Up

1  ScopeWord‑p. 7

The present document specifies the stage 2 of the Open Service Access (OSA).

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 22.101: "Service aspects; Service principles".
[2]
TR 21.905: "Vocabulary for 3GPP Specifications".
[3]
TS 22.127: "Service Requirement for the Open Services Access (OSA); Stage 1".
[4]
TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[5]
TS 22.141: "Presence service; Stage 1".
[6]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[7]
TS 23.141: "Presence service; Architecture and functional description; Stage 2".
[8]
TS 23.140: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[9]
TS 23.271: "Location Services (LCS); Functional description; Stage 2".
[10]
ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
Up

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TS 22.101, TR 21.905 and the following apply:
applications:
software components providing services to end-users by utilizing Service Capability Features
Home Environment (HE):
operator responsible for overall provision of services to users
Home Environment Value Added Service Provider:
home service provider to users other than the operator
interface:
listing and semantics of the methods and attributes provided by an object that belongs to a Service Capability Feature
OSA API:
standardized API used by applications to access Service Capability Features
OSA Internal API:
standardized API between framework and service capability servers
Service Capabilities:
See TS 22.127.
Service Capability Feature (SCF):
See TS 22.127.
Service Capability Server (SCS):
Functional Entity providing OSA interfaces towards an application
Value Added Service Provider:
service provider to users other than the operator
Up

3.2  AbbreviationsWord‑p. 8

For the purposes of the present document, the abbreviations given in TS 22.101, TR 21.905 and the following apply:
API
Application Programming Interface
HE
Home Environment
HE-VASP
Home Environment - Value Added Service Provider
HSS
Home Subscriber Server
IMS
IP Multimedia core network Subsystem
ISC
IMS Service Control
MRF
Media Resource Function
MRFC
Media Resource Function Controller
MRFP
Media Resource Function Protocol
OSA
Open Service Access
SCF
Service Capability Feature
SCS
Service Capability Server
S-CSCF
Serving - Call Session Control Function
SMS-C
Short Message Service - Center
SOAP
Simple Object Access Protocol
VASP
Value Added Service Provider
Up

4  OSA support of VASP

The OSA APIs may be used by the Home Environment, by Value Added Service Providers (VASPs) and Home Environment Value Added Service Providers (HE-VASPs).
OSA is optimized to support HE-VASPs as the user subscription information is owned and managed by the Home Environment, i.e. the Home Environment knows which users are subscribed to the service implemented by the OSA application, and if the service is activated or not.
Specific methods are specified in OSA Service Capability Features, permitting:
  • An OSA application to request user related event notifications pertaining to any subscribed user for which the service implemented by the application is activated.
  • The OSA SCS to report user related event notifications in which it explicitly identifies the user to which the event applies.
  • An OSA application to request a function to be applied to all current subscribed users for which the service implemented by the application is activated.
The OSA SCS can report user related events to the OSA application, without the application having explicitly subscribed to the event (events to be reported have been agreed between the Home Environment and the HE-VASP by other means, e.g. in their service level agreement).
This functionality is supported by all relevant Service Capability Features, like call and session control SCFs, user status, and user location.
Up

Up   Top   ToC