SOAP bindings for Call Notification

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

NGSI Common Definitions

Enabler Release Definition for LPP Extensions (LPPe)

Enabler Release Definition for Parlay Service Access

Lightweight Machine to Machine Architecture

Enabler Release Definition for Application Layer Security Common Functions

Enabler Release Definition for Rich Communication Centre

Parlay Service Access Architecture

Lightweight Machine to Machine Architecture

Enabler Release Definition for LPP Extensions (LPPe)

Enabler Release Definition for Converged Personal Network Service

Enabler Release Definition for Standard Transcoding Interface

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

OMA Management Object for MMS

OMA Management Object for Mobile_

Lightweight M2M Event Log Object (LwM2M Object EventLog)

Client Side Content Screening Framework Architecture

Enabler Validation Plan for the RESTful Network API for OMA Push

OMA Push Management Object

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

Enabler Test Specification for Device Management

Enabler Test Specification for RCS Conformance

Enabler Test Specification for Device Management

Point-to-Multipoint Push Requirements

RESTful bindings for Parlay X Web Services - Payment

Enabler Release Definition for MMS

Enabler Release Definition for Smartcard-Web-Server

OMA Device Management Tree and Description Serialization

Client Profile of OMA Device Management v1.3

Mobile Search Framework Architecture

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

Security Common Functions Architecture

RESTful Network API for Notification Channel

OneAPI Profile of RESTful Network APIs

OMA PoC Endorsement of OMA IM TS

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

OneAPI Profile of RESTful Network APIs

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

Parlay Service Access Requirements

RESTful Network API for Chat

Presence SIMPLE Architecture

White Paper on M2M Device Classification

Firmware Update Management Object

RESTful Network API for Zonal Presence

Software Component Management Object

Continues the Technical Activities Originated in the SyncML Initiative

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

Push Security Requirements

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

RESTful Network API for Third Party Call

Lightweight Machine to Machine Requirements

Enabler Test Specification for Device Management

Software Component Management Object

OMA Offline Charging Interface

Software Component Management Object (SCOMO)

Class Conformance Requirements

Software and Application Control Management Object

Enabler Test Specification for RCS Conformance

OMA PoC Document Management

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

OMA PoC Document Management

CPM Interworking Function

RESTful Network API for Short Messaging

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

Management Objects for ZigBee Devices

Enabler Test Specification for Device Management

Specification Change Document

OMA Offline Charging Interface

Scalable Vector Graphics (SVG) for the Mobile Domain

PoC XDM Specification

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

Specification Information Note

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

White Paper on UAProf Best Practices Guide

RESTful Network API for Messaging

Location in SIP/IP core Architecture Approved Version Jan 2012

[OMA-Template-Spec I]

Generic Open Terminal API Framework (GotAPI)

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

Provisioning Smartcard

RESTful Network API for Network Message Storage

OMA Device Management Bootstrap

General Service Subscription Management Technical Specification

OMA Device Management Protocol

Generic Open Terminal API Framework (GotAPI)

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

NGSI Context Management

RESTful Network API for Roaming Provisioning

RESTful Network API for FileTransfer

Location in SIP/IP core Specification Candidate Version Aug 2010

Specification Information Note

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

OMA DRM Rights Issuer Common Domain Profile

OMA Device Management Bootstrap

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

XML Document Management (XDM) Specification

XML Document Management (XDM) Specification

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

Firmware Update Management Object

CPM Message Store using RESTFul API

Transcription:

SOAP bindings for Call Notification Candidate Version 1.0 07 Dec 2010 Open Mobile Alliance OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 2 (10) 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-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 3 (10) Contents 1. SCOPE... 4 2. REFERENCES... 5 2.1 NORMATIVE REFERENCES... 5 2.2 INFORMATIVE REFERENCES... 5 3. TERMINOLOGY AND CONVENTIONS... 6 3.1 CONVENTIONS... 6 3.2 DEFINITIONS... 6 3.3 ABBREVIATIONS... 6 4. INTRODUCTION... 7 4.1 VERSION 1.0... 7 5. WSDL FOR CALL NOTIFICATION... 8 APPENDIX A. CHANGE HISTORY (INFORMATIVE)... 9 A.1 APPROVED VERSION HISTORY... 9 A.2 DRAFT/CANDIDATE VERSION 1.0 HISTORY... 9 APPENDIX B. STATIC CONFORMANCE REQUIREMENTS (NORMATIVE)... 10 B.1 SCR FOR NGSI-5 SERVER... 10 B.2 SCR FOR NGSI-5.CN SERVER... 10 Figures None. Tables Table 1 SCR for NGSI-5 Server Functions... 10 Table 2 SCR for NGSI-5 Call Notification Server Functions... 10

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 4 (10) 1. Scope This document specifies the SOAP binding for NGSI-5 interface [NGSI Call Control and Configuration]. As NGSI-5 is an extension to Parlay-X Part 3 [3GPP TS 29.199-3] and all the corresponding WSDL files from Parlay-X Part 3 are affected by the extensions defined by NGSI-5, all the corresponding WSDL files are provided together.

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 5 (10) 2. References 2.1 Normative References [3GPP TS 29.199-3] [NGSI Call Control and Configuration] [NGSI-SUP-CallNotification] [RFC2119] [SCRRULES] 2.2 Informative References Open Service Access (OSA) Parlay X web services; Part 3:Call Notification, 3GPP TS 29.199-3 Rel.8, URL:http://www.3gpp.org/ NGSI Call Control and Configuration, Open Mobile Alliance, OMA-TS- NGSI_Call_Control_and_Configuration-V1_0, URL:http://www.openmobilealliance.org/ WSDL package for NGSI Call Notification, Open Mobile Alliance, OMA-SUP- WSDL_ngsi_call_notificaiton-V1_0, URL:http://www.openmobilealliance.org/ Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt SCR Rules and Procedures, Open Mobile Alliance, OMA-ORG- SCR_Rules_and_Procedures, URL:http://www.openmobilealliance.org/ [OMADICT] Dictionary for OMA Specifications, Version 2.8, Open Mobile Alliance, OMA-ORG-Dictionary-V2.8, URL:http://www.openmobilealliance.org/

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 6 (10) 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 None in this version. 3.3 Abbreviations NGSI NGSI-S OMA Next Generation Service Interfaces SOAP Bindings for NGSI Open Mobile Alliance

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 7 (10) 4. Introduction The NGSI_Call_Notification_Extension interface extends Parlay-X Call Notification interface (Part 3). The XSD file and WSDL files from Parlay-X Part 3 are used as basis for the extended data files. To ensure consistency for the usage of the extended Parlay X Part 3 interface and to respect the references between the interfaces and the related XSD, this specification provides all updated WSDL and XSD files. 4.1 Version 1.0 This specification provides the SOAP binding for the NGSI-5 interfaces as specified in [NGSI Call Control and Configuration]. The WSDL representation and the verification files as listed in section 5 are contained in the support file [NGSI-SUP-CallNotification].

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 8 (10) 5. WSDL for Call Notification The WSDL representation for the NGSI-5 interface is contained in the support file [NGSI-SUP-CallNotification] and consists of the following files: ngsi_call_direction_interface-v1_0.wsdl ngsi_call_direction_service-v1_0.wsdl ngsi_call_direction_manager_interface-v1_0.wsdl ngsi_call_direction_manager_service-v1_0.wsdl ngsi_call_notification_interface-v1_0.wsdl ngsi_call_notification_service-v1_0.wsdl ngsi_call_notification_manager_interface-v1_0.wsdl ngsi_call_notification_manager_service-v1_0.wsdl ngsi_call_notification_types-v1_0.xsd The above WSDL files can be verified using the following files: ngsi5_wsdl2java_axis-1_4.bat ngsi5_wsdl2java_axis2-1_4_1.bat

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 9 (10) Appendix A. Change History (Informative) A.1 Approved Version History None yet. Reference Date Description A.2 Draft/Candidate Version 1.0 History Document Identifier Date Sections Description Draft Versions: OMA-TS-NGSI_S_Call_Notification-V1_0 Candidate Version: OMA-TS-NGSI_S_Call_Notification-V1_0 12 Aug 2010 All Skeleton document 16 Sep 2010 1, 2.1, 4 Add Intro, Scope, and Reference section text CRs implemented: OMA-ARC-NGSI-2010-0177R01- CR_TS_Call_Notification_Intro_Scope_Refs 24 Sep 2010 2.1, Annex B Added SCR, fixed typo in reference section. CRs implemented: OMA-ARC-NGSI-2010-0197R01-CR_SCR_for_Call_Notification_TS 08 Oct 2010 Annex B Modifications for NGSI-5.CN Server CRs implemented: OMA-ARC-NGSI-2010-0205- CR_SCR_for_Call_Notification_ 21 Oct 2010 All Groups Review during conference call 21 October 2010 07 Dec 2010 All Status changed to Candidate by TP: OMA-TP-2010-0500- INP_NGSI_S_V1_0_ERP_for_Candidate_Approval

OMA-TS-NGSI_S_Call_Notification-V1_0-20101207-C Page 10 (10) Appendix B. Static Conformance Requirements (Normative) The notation used in this appendix is specified in [SCRRULES]. The Reference column of the SCR tables below refers to a section in this document. Additionally, this column also refers to the appropriate section in the TS of the abstract interface definitions, if applicable. Additionally, this column also refers to the appropriate section in the TS of the abstract interface definitions, if applicable. Hereby, CCC-x stands for section x in [NGSI Call Control and Configuration] and PX3-x stands for section x in [3GPP TS 29.199-3]. B.1 SCR for NGSI-5 Server Item Function Reference Requirement NGSI-5-SUPPORT-S- Support for the Call Control 5, CCC-6.1 001-M extension Interface (NGSI-4) NGSI-5-SUPPORT-S- 002-M Support for the SOAP/ XML request & response format B.2 SCR for NGSI-5.CN Server Table 1 SCR for NGSI-5 Server Functions Item Function Reference Requirement NGSI-5-CN-S-001-M Support for the Call Direction 5, PX3-8.1 Interface NGSI-5-CN-S-002-M Support for Call Direction to 5, PX3-8.1.5 handle Busy, NotReachable, NoAnswer, CalledNumber call events NGSI-5-CN-S-003-O Support for Call Direction to handle the call event with a list of participants to be forward in forwarding 5, PX3-8.1.1 CCC-6.1.3.1 NGSI-5-CN-S-004-O NGSI-5-CN-S-005-O NGSI-5-CN-S-006-O NGSI-5-CN-S-007-O Support for Call Direction to handle the call event with ring back media extension Support for Call Direction to handle the call event with alerting media extension Support for Call Direction to handle the call event with address display setting extension for anonymous call Support for Call Direction to handle the case Busy with call recording extension 5 5, PX3-8.1.1 CCC-6.1.3.1 5, PX3-8.1.1 CCC-6.1.3.1 5, PX3-8.1.1 CCC-6.1.3.1 5, PX3-8.1.1 CCC-6.1.3.1 Table 2 SCR for NGSI-5 Call Notification Server Functions