Presentation is loading. Please wait.

Presentation is loading. Please wait.

ICEBERG Release Version 0

Similar presentations


Presentation on theme: "ICEBERG Release Version 0"— Presentation transcript:

1 ICEBERG Release Version 0
24-Feb-19 ICEBERG Release Version 0 In this presentation I’ll be talking about the Iceberg software release. The purpose of this is to walk-through the release, give an idea of what’s in it, some of the neat capabilities like APIs for extension, features like any-to-any communication and service handoff. The ICEBERG Team Summer 2000 Retreat

2 The ICEBERG Team, Summer 2000 Retreat
24-Feb-19 Overview Background Components in the release Feature set Interfaces APIs for extension Limitations Plans for next release Here's the outline of the talk... I'll first present the components that are there in the release Then, a high level picture of the set of capabilities that are possible with these components The main interfaces between these components One of the claimed features of Iceberg is its extensibility to new end-points and services. So I'll talk about the APIs that allow such an extension, in this particular release Then I'll mention some of the limitations, and how we plan to address these in an end-of-summer release. February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

3 ICEBERG Goals: Potentially Any Network Service
24-Feb-19 ICEBERG Goals: Potentially Any Network Service Same service in different networks Service handoff between networks 2-way Paging PSTN GSM/CDMA IAP IAP IAP Extensible network environment Addressing access-device and access-network heterogeneity IP IAP WIP High BW IP core Diverse access links IAP February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

4 ICEBERG Goals: Personal Mobility
Speech-to-Text Speech-to-Voice-Attached- Call-to-Pager/ -Notification -to-Speech All compositions of the above! Universal Inbox Policy-based Location-based Activity-based February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

5 The ICEBERG Team, Summer 2000 Retreat
ICEBERG Goals Go beyond 3rd generation cellular Infrastructure for hybrid services Work in the wide-area Ease of deployment Robust signaling, high availability Secure billing issues February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

6 ICEBERG Architecture: An Overview
24-Feb-19 ICEBERG Architecture: An Overview Access Network Plane PSTN GSM Pager IAP IAP IAP A ICEBERG Network Plane SF iPOP NY iPOP B PR CA PAC APC NMS SF iPOP NY iPOP First, we begin with a 10, 000 feet view of the ICEBERG network We envision a number of ICEBERG Service Provider, they provide integrated communication services For each ICEBERG Service Provider, there are Point of Presences at different geographical locations. Clearing House ISP Plane ISP1 ISP2 ISP3 February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

7 Components in the Release
Client IAPs Outgoing calls Call Agent (CA) ICEBERG Access Points (IAPs) Preference Registry (PR) Automatic Path Creation Service (APC) Incoming calls Name Mapping Service (NMS) Server IAPs ICEBERG Point of Presence (iPOP) February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

8 Components in the Release
VAT IAP VAT GSM GSM IAP Testbed CA Jukebox IAP Ninja PR Jukebox Pref. Mgr. GUI MediaManager IAP APC Voic IAP MediaManager NMS Service iPOP Mail-push Client IAP Voic Mail-store February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

9 The ICEBERG Team, Summer 2000 Retreat
Requirements Ninja 1.5 iSpace for service platform NinjaRMI for communication Hardware Linux cluster Scaling not too good Use of NinjaRMI Process-per-operator-per-path model for APC February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

10 Capabilities: Any-to-Any Communication
Calls from friends Anonymous callers s from important business associates Calls during office hours Read through MediaManager Preference-based redirection Device-type and name independence February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

11 Capabilities: Service Handoff
February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

12 Capabilities: Service Handoff
February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

13 Capabilities: Adding new IAPs
H.323 IAP Stock Quotes IAP Push iPOP Access Yahoo Calendar IAP February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

14 Capabilities: Adding to APC
Front-end Back-end APC Operators + Connectors PCM GSM RMI MP3 PCM UDP Text PCM RTP PCM G.723 February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

15 The ICEBERG Team, Summer 2000 Retreat
24-Feb-19 Overview Background Components in the release Feature set Interfaces APIs for extension Limitations Plans for next release Here's the outline of the talk... I'll first present the components that are there in the release Then, a high level picture of the set of capabilities that are possible with these components The main interfaces between these components One of the claimed features of Iceberg is its extensibility to new end-points and services. So I'll talk about the APIs that allow such an extension, in this particular release Then I'll mention some of the limitations, and how we plan to address these in an end-of-summer release. February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

16 Interfaces between Components
NMS1 NMS2 PR1 PR2 CA 1 CA 2 IAP 1 IAP 2 APC 1 APC 2 NinjaRMI Soft-state signaling for session maintenance February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

17 Interfaces with Specific Services
APC Service int createPath(source, destination)  returns pathID Source and Destination description: Machine address Connector specification: RMI/UDP/HTTP/RTP void destroyPath(int pathID) void changePath(int pathID, newSrc) MediaManager Service String[] getFolders(username) MediaMessage[] getList(username, folder, num-msgs) ContentObject getMsgContent(contentID, int type)  returns one of: text transcript, text summary, audio summary multiple audio formats possible February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

18 API’s for Extension: Adding IAPs
Setup(), Terminate(), DTMF(), ServiceHandoff() CA Setup(), Terminate(), DTMF() Device- or service-specific part Generic part APC StartConnection(), CleanUp() Extend IAPWithCA Implement IAPIF February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

19 API’s for Extension: Adding Operators
Specify I/O types Specify ADU size For process-based operators: Java-wrapper around executable I/O in STDIN/STDOUT Specify executable G.723 codec added in 2hrs APC Operator 1 New Operator Operator 2 Operator 3 Extend Operator Implement OperatorIF February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

20 The ICEBERG Team, Summer 2000 Retreat
24-Feb-19 Overview Background Components in the release Feature set Interfaces APIs for extension Limitations Plans for next release Here's the outline of the talk... I'll first present the components that are there in the release Then, a high level picture of the set of capabilities that are possible with these components The main interfaces between these components One of the claimed features of Iceberg is its extensibility to new end-points and services. So I'll talk about the APIs that allow such an extension, in this particular release Then I'll mention some of the limitations, and how we plan to address these in an end-of-summer release. February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

21 The ICEBERG Team, Summer 2000 Retreat
Limitations in v0 No heart-beat between IAP and CA require iPOP in a vSpace cluster IAP stub communicates with periodic state updates (keep-alive messages) APC supports only UDP connectors between operators UDP Any February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

22 Limitations in v0 (Continued)
APC issues ties operators to specific connectors process per operator model (scaling problems) pipes for communication (huge delays due to buffering) path restricted within a cluster Issues with path control hard-state protocol for setup and tear-down (easy to fix) no flow control (more difficult to fix) February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

23 Limitations in v0 (Continued)
Naming service not distributed Soft-state update not enough for user-level signaling between end-points need reliable propagation need instantaneous propagation e.g., DTMF IAP 1 CA 1 CA 2 IAP 2 February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

24 The ICEBERG Team, Summer 2000 Retreat
Plans for Next Release Port to vSpace fault-tolerant communication between the IAP and the CA inherit scaling features Fix (some of) APC issues remove process-per-operator model remove coupling between operators and connectors soft-state for path maintenance February 24, 2019 The ICEBERG Team, Summer 2000 Retreat

25 The ICEBERG Team, Summer 2000 Retreat
Feedback Evaluation strategy Security issues Things to fix in next release Thoughts on more IAPs Deployment issues Questions... February 24, 2019 The ICEBERG Team, Summer 2000 Retreat


Download ppt "ICEBERG Release Version 0"

Similar presentations


Ads by Google