streamlining network innovation. welcome and introductions 2 andrew white vice president, technology...
Post on 18-Dec-2015
221 Views
Preview:
TRANSCRIPT
Streamlining Network Innovation
Welcome and Introductions
2
Andrew WhiteVice President,Technology and StandardsATIS
Agenda – Inaugural Meeting
• Welcome and Introductions• DSI – ORCA Meeting Objectives• The DSI’s First Project: ORCA• ORCA Testing and Support Requirements• DSI Overview• DSI Operating Procedures• Next Steps• Open Floor / Questions / Discussion• Adjournment
3
4
Objectives
Introduce “ORCA”, Open
Real-time Communications
APIs.
Discuss the process of
integrating ORCA APIs into web applications.
Demonstrate how DSI defines and directs projects
that deliver network value.
Share the framework for
combining open source and standards.
Address questions
regarding next steps.
The DSI’s First Project: ORCA
5
Jim McEachernSenior Technology ConsultantATIS
Dan DrutaPrincipal Architect, Service Standards GroupAT&T
6
The Origins of ORCA
• The Technology and Operations (“TOPS”) Council undertakes important strategic initiatives based on Board direction to meet the industry’s long-term technology needs and achieve member business objectives.
– The Unified Client Architecture Focus Group (UCA-FG) was launched to assess tools that will enable software developers to integrate core network capabilities into their applications.
• UCA-FG considered opportunities for WebRTC clients to access network functionality in a network-independent manner.
• The UCA-FG’s work led to the creation of ORCA, or Open Real-time Communications APIs.
Device Solutions
Examine opportunities
to extend core network capabilities
into any device
Initial Focus - WebRTC
7
Enhanced Device Capabilities
• A WebRTC-enabled web browser – on any device – has the capability to deliver real-time audio and video.– WebRTC (real time communication) enables real-time
audio and video as part of other web-based applications.
– Potential to enable new capabilities for communications services:
• Customer interaction• Conferencing• Interactive sites• Integration of voice/videocommunications into a web environment
8
WebRTC Strategic Opportunity• Proposed WebRTC services do not leverage network
functionalities.
• Opportunity exists for WebRTC developers to connect to service providers’ networks and leverage network services:– QoS – Security– Interoperation– Reliability– Routing infrastructure/
session control/presence
WebRTC specifies media handling for real-time communications,but does not specify signaling for call setup.
E2E Quality of Experience Across Multiple Domains
9
Solution: Open Real-time Communications API
• Provide developers with ability to access network functions.
• JavaScript Library with APIs is necessary to access and utilize network services:– Enables developers to more easily
develop applications and enhances time-to-market
– Promotes service providers’ core capabilities that may otherwise not be leveraged
– Provides consistent access to network functionality
Browser* Browser*
WebRTC
ORCA
(SP’s Network)
10
Device Solutions
Application developers connect to service
providers’ networks and leverage IMS services.
Enable new capabilities for communications services….
ORCA
(SP’s Network)
Any Device
Any Device
11
12
ORCA
• ORCA is an open source project hosted on GitHub.
– Individuals are free to join and contribute
• Client-side JavaScript is open source and royalty free.
– Links to network specific “transport libraries” at run time
• ORCA provides application developers with normalized call control APIs.
– Can be extended to include additional APIs and JavaScript libraries
WebRTC enabled Browser
DeviceTransport
Specific APIs (Client)
Invoke w3C APIs
W3C WebRTC APIs
WebRTC Gateway
(WebSockets)JavaScript WebApp
IMS
Other Browser
SRTP
Web Server
Call Control API
Transport Specific APIs
(Client)
WebRTC Gateway(RESTFul)
Gm
Gm
IETF
Gm
OMA
Other Client(RCS)
WebRTC Gateway(Other)
Other
13
ORCA: High-level Architecture
Call Control
Transport Library
WebRTC Gateway
Call Control
Transport Library
WebRTC Gateway
Call Control
Transport Library
WebRTC Gateway
Normalized Call Control Library(Open Source)
Transport Library
WebRTC Gateway
IMS Core
Transport Library
WebRTC Gateway
Transport Library
WebRTC Gateway
Runs
in th
e br
owse
rRu
ns in
the
netw
ork
IMS Core
REST
Web
Sock
ets
Oth
er
REST
Web
Sock
ets
Oth
er
Vendor specific Vendor specific Vendor specific Vendor specific Vendor specific Vendor specific
14
Phase 1: Harmonization for Call Control API
Potential WebRTC Based Communications Services
15
Call control:• Incoming call alert (including
callerID info)• Call origination • Call termination• Call hold• Call transfer• Prioritize and transport SDP offer
to remote end• Add/drop additional party
(conferencing)• Call waiting alert (including
callerID info)• Add/drop stream (video, sharing,
IM)
Presence:• Status control• Subscription• Change notification
Registration:• Client registration• Authentication (leveraging UICC?) CS Fallback (local API only):• Call handoff (webRTC->CS, CS-
>webRTC)
Other:• Network address book access (at
least retrieve access)• Network flow selection (in support
of QoS)• Network selection (wifi, 3G, 4G,
etc)
16
Traditional Interoperability Approach
1.Develop Standards
2.Compliant Implementations
3.Network Deployment
Standards Promote Interoperability
17
Interoperability in the Internet Age
1.Prototype2.Refine
3.Standardize(where necessary)
Rough Consensus, and Running Code
18
• ORCA is not a traditional standards project.
• Requires different skills:
– Contributions are actual code
– Must understand software development process
– Experience with Git
– Open source expertise
• Get involved in ORCA today
ORCA: A Different Kind of Project
ORCA Testing and Support Requirements
19
Dave RobinsonChief Video ArchitectIP Routing and Transport DivisionAlcatel Lucent
20
ORCA API Testing
• Applications that use ORCA APIs will require infrastructure to support testing and integration.
• Multiple levels of testing support are envisaged:
– Basic “reflector” to run in developer environment
– Test IMS environment
– Service Provider / Vendor developer programs
– Live network testing
• This presentation will discuss immediate requirements for a basic “reflector”.
21
ORCA Testing: Basic Reflector
• Aim:
– Allow developers to test client implementations
– Run entirely within developer infrastructure
– Be available on GitHub to download by developers
• Not supported:
– High availability
– Scaling for multiple clients
– High performance
Provides first level test environment
22
Reflector Test Configuration
ORCA
Trans Lib
Client App
WebRTC Browser
ORCA
Trans Lib
Client App
WebRTC Browser
Basic Reflector
Developers test environment
Test Machine 1 Test Machine 2
ORCA APIORCA API
Basic reflector protocol
23
Functions Supported
• The basic backend “reflector” will support:– Register: allow client to register willingness to
receive WebRTC request – Call: allow a second client to initiate a call to a
previously allocated client – Reject: allow the registered client to reject the call
request– Accept: allow registered clients to accept the call
request– Disconnect: allow either party to terminate the
call– Event: notify the parties in the call of a change of
status (incoming call, call accept, call reject, disconnect etc.)
24
Future enhancements
• PSTN: Enable calls to/from PSTN / PLMN• NAT / Firewalls: Support traversing of
firewalls• Security: Provide authentication and
authorisation• Robustness: Be highly available and
scalable
25
Summary
• The basic backend “reflector” will allow application developers to complete initial verification of applications with ORCA functionality.
• Additional backend functionality will be made available as required.
Device Solutions Initiative (DSI)Overview
26
Jim McEachernSenior Technology ConsultantATIS
Problem StatementIntegrating network-based service enablers such as call signaling or network control requires developers to adapt applications to use unique network APIs for each service provider. Additionally, attracting application developers to traditional standards is challenging - they primarily contribute to open source projects.
SolutionThe DSI provides a framework to support and develop open source projects. Service provider and supplier members work together with application developers to provide client-side functionality that consistently exposes core network capabilities into real-time communications applications.
27
DSI Streamlines Network Innovation
• Existing service provider APIs offer similar functionality
• But, developer rework is required to accommodate service providers’ unique implementations
• The result:– Developer avoidance– Diluted scale– Decreased utilization
of service provider infrastructure
Service Provider A Interface
Service Provider B Interface
?
Similar Core
Functions
Service Provider C Interface
?
Developer
Developer
28
Problem Statement: Fragmented APIs
• Service providers’ unique APIs remain unchanged, but client-side abstraction normalizes the APIs
• APIs now operate consistently, reducing developer rework
• The result:– Developer adoption– Industry scale– Increased utilization
of service provider infrastructure
Service Provider A Interface
Service Provider B Interface
DSI provides a consistent mechanism to expose network APIs.
Service Provider C Interface
DSI
Insi
deSimilar Core
Functions
29
Solution: API Portability
• DSI can also provide client-side functionality
• Support and simplify interaction with network (e.g. normalize browser implementation of WebRTC)
• The result:– Complementary
functions– Simplify access to
network functionality– Additional value for
DSI and for the network
Service Provider A Interface
Service Provider B Interface
DSI libraries also provide client-side functionality.
Service Provider C Interface
DSI
Insi
deSimilar Core
Functions
30
Java
Scrip
t Lib
rarie
s
Opportunity: Beyond APIs
Developers• One-stop, vendor-neutral solution extends reach• Consistent, standardized APIs ease development
challenges• Addressable market size improves return on
innovation• Write-once, run anywhere approach reduces
adaptation costs• Contribute to direction of projects
Service Providers• Aggregate scale drives developer engagement• Innovative offerings strengthen retail relationships
with end-users• WebRTC clients expand utilization of IMS
infrastructure• Leveraging existing service enablers improves
return on invested capital
End Users• Innovative product offerings improve end user
experience• Applications are able to be ported• Service reliability is enhanced through network
integration• Zero install client simplifies communications
services
Suppliers• Enhanced product offerings facilitate service
provider deployment of web-enabled applications• Increased use of IMS infrastructure accelerates
deployment• WebRTC adaptation leverages existing
infrastructure• Increased flexibility promotes innovation
31
DSI Value to Marketplace
Today’s Reality
32
Application developers:• Do not participate in
standards forums• Contribute to open
source projects
Devices• Client
Applications• JavaScript
libraries
Solutions• Communications• Network• Management
The DSI Approach
33
Devices• Client
Applications• JavaScript
libraries
Solutions• Communications• Network• Management
DSI embraces a run-time linkage between
open source innovation and reliable network
solutions
Where Open Source Enables
Network Services
Define & Influence DSI’s Strategic Direction
DSI members identify and prioritize projects to deliver network value to web-connected devices that support downloadable applications.
34
Direct open source projects
Define network facing functionality requirements to operationalize new capabilities
Evaluate new projects in emerging markets, such as M2M
Prioritize APIs for adoption across DSI member companies
35
DSI operates with fair, open and consensus-based processes.
Work progresses primarily through virtual meetings and electronically.
Flexible processes facilitate innovation through rapid output and implementation. Developers can participate based on
contribution and expertise.
Intellectual property rights policies provide flexibility for members to develop a broad set of solutions ranging from open
source software to industry standards and guidelines.
DSI Operates By Consensus
• ORCA gives developers a single interface to simplify network signaling for real-time communications applications based on WebRTC by providing open source, client-side bindings and SDKs.
• Client-side functionality is also included in ORCA libraries.
• Developers participate in ORCA open source software development.
36
Connect, Simply.
ORCA – Open-Real-Time Communications API
DSI’s First Project is Underway
37
Membership fees valid for participation from launch through the year end of 2014.
Who should join?
•Service providers and suppliers •Software / cloud companies•Non-ATIS members are eligible to join
How much does it cost?
•Consolidated ATIS members - no additional fee•Non-consolidated ATIS members - $10,000•Non-ATIS members - $15,000
Can My Company Join?
38
Visit the DSI Website:www.atis.org/dsi
Contact: Jim McEachernjmceachern@atis.org
Learn More
DSI Operating Procedures
39
Thomas GoodeATIS General Counsel
40
• A draft of the OP that will govern DSI operations is available.
• Approval of the OP will be one of the first orders of business of the DSI membership.
• Objectives for DSI OP:– Lightweight, flexible procedures– Alternative IPR models to allow development of a broad
range of deliverables (including open source)– A process for collaboration between DSI and the open
source community
DSI Operating Procedures (OP)
41
• Who can participate (Section 2)? – Participation in the DSI is open to all ATIS Members, as well
as to other service providers, manufacturers, distributors and developers of communications, entertainment and information technology products/services
– DSI will collaborate with the open source community to allow for developer input
• How are DSI decisions reached (Sections 5.3, 7)?– DSI members will reach decisions via consensus;
consensus is reached when substantial agreement has been reached among participants
Issues Addressed in the DSI Operating Procedures
42
• How can new projects be launched (Section 5)?– New projects are proposed in writing; DSI members
approve new projects via consensus.
• How will DSI be structured? – While it is anticipated that work will generally be
completed through Project Management Committees (PMC), DSI members may choose to establish subcommittees or task forces
– DSI and any subgroups will be led by Chairs/Vice Chairs (or Co-Chairs) elected by the DSI members
– Work will be completed via virtual or face-to-face meetings of PMCs
Issues Addressed in the DSI Operating Procedures
• What types of deliverables can be developed (Section 6, 9)? – DSI members will be able to choose to develop a variety of
deliverables, from open source software to standards– At the initiation of a project, the DSI membership will
determine which of two intellectual property rights policies will apply to the work:
1. A royalty-free IPR policy; or 2. A RAND policy based on ATIS’ established policy.
– The IPR policy governing a project will be established at the initiation of a project via the consensus of the membership
43
Issues Addressed in the DSI Operating Procedures
• How will DSI collaborate with the open source community (Annex C)?– Open source software developed by the DSI will be posted
on an appropriate open source repository– Developers may provide feedback on the software– Some developers (those demonstrating the appropriate
skillsets) may be invited to be part of the PMC, which can approve submissions)
• Other issues that are addressed in the draft OP:– Appeals Process (Section 12)– Revision Process (Section 13)– Due Process Considerations (meeting and election notices,
meeting notes, etc.) (Sections 4, 8, etc.)
44
Issues Addressed in the DSI Operating Procedures
DSI consists of:• Project governance structure
• Process for initiating new projects
• One or more projects• Each project is largely self-
governing, within the structure defined by DSI
DSI
Project “Dolphin”Project ORCA
PMC
GitHub
Project creation process
45
DSI Structure
46
DSI Workflow Example
47
Questions, Comments
• If there are any questions regarding or suggested revisions to the DSI Operating Procedures, please let me know:
Thomas GoodeATIS General Counsel1.202.434.8830tgoode@atis.org
Next Steps
48
Jim McEachernSenior Technology ConsultantATIS
49
Next Steps
• DSI is open for business
– New members are welcome
– Next DSI meeting in 1Q2014
• ORCA Project is active.
– www.orcajs.org
• Next ORCA Project Management Committee meeting is December 3rd.
– DSI members only
Open Floor / Questions / Discussion
50
Adjournment
51
top related