Reference Release Definition for Parlay/OSA(Open Service Access) In OMA Service Environment (PIOSE)

Similar documents
Parlay Service Access Architecture

Lightweight Machine to Machine Architecture

SOAP bindings for Call Notification

Enabler Release Definition for Parlay Service Access

Standardized Connectivity Management Objects HTTP Proxy Parameters For use with OMA Device Management

Enabler Release Definition for Standard Transcoding Interface

Enabler Release Definition for Rich Communication Centre

Lightweight Machine to Machine Architecture

Enabler Release Definition for LPP Extensions (LPPe)

Enabler Release Definition for LPP Extensions (LPPe)

Enabler Release Definition for Converged Personal Network Service

Client Side Content Screening Framework Architecture

Enabler Release Definition for Application Layer Security Common Functions

OMA Push Management Object

Enabler Validation Plan for the RESTful Network API for OMA Push

NGSI Common Definitions

Lightweight M2M Event Log Object (LwM2M Object EventLog)

Standardized Connectivity Management Objects 3GPP Circuit-Switched Data Bearer Parameters For use with OMA Device Management

Enabler Release Definition for Smartcard-Web-Server

OMA Management Object for MMS

Point-to-Multipoint Push Requirements

OMA Management Object for Mobile_

Standardized Connectivity Management Objects WAP Proxy Parameters For use with OMA Device Management

OMA Device Management Tree and Description Serialization

Enabler Test Specification for RCS Conformance

Client Profile of OMA Device Management v1.3

Parlay Service Access Requirements

Enabler Test Specification for Device Management

Enabler Test Specification for Device Management

Mobile Search Framework Architecture

OMA-ETS-DL-OTA-v1_ a Page 1 (24)

Enabler Release Definition for MMS

Security Common Functions Architecture

White Paper on M2M Device Classification

Presence SIMPLE Architecture

Firmware Update Management Object

Charging Data. Candidate Version Jul Open Mobile Alliance OMA-DDS-Charging_Data-V1_ C

Continues the Technical Activities Originated in the SyncML Initiative

Push Security Requirements

Enabler Release Definition for Mobile Location Protocol (MLP) Candidate Version Mar 2004

Lightweight Machine to Machine Requirements

RESTful bindings for Parlay X Web Services - Payment

Class Conformance Requirements

Software Component Management Object

OMA PoC Endorsement of OMA IM TS

RESTful Network API for Notification Channel

OneAPI Profile of RESTful Network APIs

Software Component Management Object

OneAPI Profile of RESTful Network APIs

OMA Offline Charging Interface

RESTful Network API for Chat

IM XDM Specification. Candidate Version Aug Open Mobile Alliance OMA-TS-IM_XDM-V1_ C

WAP General Formats Document WAP-188-WAPGenFormats Version 10-Jul-2001

RESTful Network API for Zonal Presence

Enabler Test Specification (Interoperability) for MMS 1.3 Candidate Version 15 Jun 2006

White Paper on UAProf Best Practices Guide

Enabler Test Specification for Device Management

Software Component Management Object (SCOMO)

WAP-Sync-Spec. Data Synchronisation Specification Version 30-May Wireless Application Protocol WAP-234-SYNC a

Software and Application Control Management Object

Enabler Test Specification for RCS Conformance

Specification Change Document

Specification Information Note

SyncML OBEX Binding. Candidate Version Apr Open Mobile Alliance OMA-TS-SyncML_OBEXBinding-V1_ C

Location in SIP/IP core Architecture Approved Version Jan 2012

Management Objects for ZigBee Devices

PoC XDM Specification

Scalable Vector Graphics (SVG) for the Mobile Domain

Provisioning Smartcard

IETF TRUST. Legal Provisions Relating to IETF Documents. February 12, Effective Date: February 15, 2009

RESTful Network API for Third Party Call

Ecma International Policy on Submission, Inclusion and Licensing of Software

OMA Offline Charging Interface

IETF TRUST. Legal Provisions Relating to IETF Documents. Approved November 6, Effective Date: November 10, 2008

CPM Interworking Function

Cache Operation. Version 31-Jul Wireless Application Protocol WAP-175-CacheOp a

OMA Device Management Protocol

Firmware Update Management Object

Compatibility Matrix. Good Control and Good Proxy. June 4, 2018

General Service Subscription Management Technical Specification

Terms of Use. Changes. General Use.

OMA PoC Document Management

Ecma International Policy on Submission, Inclusion and Licensing of Software

Enabler Test Specification for Device Management

OMA PoC Document Management

[OMA-Template-Spec I]

Generic Open Terminal API Framework (GotAPI)

Enabler Test Report Smartcard Web Server v1.0. OMA TestFest (January 2008) Version 1st February 2008

HYCU SCOM Management Pack for F5 BIG-IP

Push using SIP. Candidate Version Apr Open Mobile Alliance OMA-TS-SIP_Push-V1_ C

Multimedia Messaging Service Architecture Overview

Generic Open Terminal API Framework (GotAPI)

OMA Device Management Bootstrap

Specification Information Note

OASIS - Artifact naming guidelines

OCTOSHAPE SDK AND CLIENT LICENSE AGREEMENT (SCLA)

Mile Terms of Use. Effective Date: February, Version 1.1 Feb 2018 [ Mile ] Mileico.com

Raspberry Pi shield board

Level of Assurance Authentication Context Profiles for SAML 2.0

ETSI TS V4.1.0 ( )

Transcription:

Reference Release Definition for Parlay/OSA(Open Service Access) In OMA Service Environment (PIOSE) Candidate Version 1.0 19 Oct 2007 Open Mobile Alliance OMA-RRELD-PIOSE-V1_0-20071019-C

OMA-RRELD-PIOSE-V1_0-20071019-C Page 2 (9) Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/useagreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the OMA IPR Declarations list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form. NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPR S REPRESENTED ON THE OMA IPR DECLARATIONS LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL. THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.

OMA-RRELD-PIOSE-V1_0-20071019-C Page 3 (9) Contents 1. SCOPE...4 2. REFERENCES...5 2.1 NORMATIVE REFERENCES...5 3. TERMINOLOGY AND CONVENTIONS...6 3.1 CONVENTIONS...6 3.2 DEFINITIONS...6 3.3 ABBREVIATIONS...6 4. RELEASE VERSION OVERVIEW...7 5. DOCUMENT LISTING FOR PIOSE V1.0...8 APPENDIX A. CHANGE HISTORY (INFORMATIVE)...9 A.1 APPROVED VERSION HISTORY...9 A.2 DRAFT/CANDIDATE VERSION 1.0 HISTORY...9 Tables Table 1: Listing of Documents in PIOSE Reference Release...8

OMA-RRELD-PIOSE-V1_0-20071019-C Page 4 (9) 1. Scope The scope of this document is limited to the Reference Release Definition of Parlay/OSA in OSE (PIOSE) V1.0 according to OMA Release process and the Reference Release document baseline listed in section 5.

OMA-RRELD-PIOSE-V1_0-20071019-C Page 5 (9) 2. References 2.1 Normative References [RFC2119] Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt [PIOSE-RD] [PIOSE-AD] Parlay/OSA in OSE Requirements, Open Mobile Alliance, OMA-RD-ParlayinOSE-V1_0, URL:http://www.openmobilealliance.org/ Parlay/OSA in OSE Architecture, Open Mobile Alliance, OMA-AD-ParlayinOSE-V1_0, URL:http://www.openmobilealliance.org/

OMA-RRELD-PIOSE-V1_0-20071019-C Page 6 (9) 3. Terminology and Conventions 3.1 Conventions The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated to be informative. 3.2 Definitions Reference Release Reference Release Definition 3.3 Abbreviations A set of specifications and/or white papers which form a formal deliverable of OMA. The release can be referenced or otherwise used to support implementable enabler releases, but it cannot by itself be implemented in products. A definition of the documents that are included in a Reference Release. OMA RRELD OSE PIOSE Open Mobile Alliance Reference Release Definition OMA Service Environment Parlay/OSA in OSE

OMA-RRELD-PIOSE-V1_0-20071019-C Page 7 (9) 4. Release Version Overview This document outlines the materials that constitute the Reference Release Definition for the Parlay/OSA in OSE (PIOSE) This reference release serves to keep the collection of materials associated for ease of use and acquisition. The purpose of PIOSE enabler is to provide guidance on how an OMA enabler implementation may take advantage of the Parlay X web services APIs and the OSA/Parlay APIs. Parlay X APIs and Parlay APIs implementations can be realized in OSE. 4.1 Version 1.0 Functionality The purpose of PIOSE enabler is to provide guidance on how an OMA enabler implementation may take advantage of the Parlay X web services APIs and the OSA/Parlay APIs. Parlay X APIs and Parlay APIs implementations can be realized in OSE.

OMA-RRELD-PIOSE-V1_0-20071019-C Page 8 (9) 5. Document Listing for PIOSE V1.0 This section is normative. Doc Ref Permanent Document Reference Description Requirement Document [PIOSE-RD] OMA-RD-ParlayinOSE-V1_0-20070615-C Requirement Document for PIOSE Version 1.0 Reference Package Architecture Document [PIOSE-AD] OMA-AD-ParlayinOSE-V1_0-20071019-C Architecture Document for PIOSE Version 1.0 Reference Package Table 1: Listing of Documents in PIOSE Reference Release

OMA-RRELD-PIOSE-V1_0-20071019-C Page 9 (9) Appendix A. Change History (Informative) A.1 Approved Version History Reference Date Description n/a n/a No prior version or- No previous version within OMA A.2 Draft/Candidate Version 1.0 History Document Identifier Date Sections Description 23 August 2007 all Initial version. Draft Versions OMA-RRELD-PIOSE-V1_0 07 Sep 2007 n/a Fixed the RRELD file name to match with cover page (OMA-RRELD- PIOSE-V1_0) Candidate Versions: OMA-RRELD-PIOSE-V1_0 19 Oct 2007 n/a Status changed to Candidate by TP TP Ref# OMA-TP-2007-0400- INP_PIOSE_V1_0_RRP_for_Candidate_Approval