1 / 10

Solving the Back End with Platform Solutions

Solving the Back End with Platform Solutions. Alex Vishnev CTO Global Convergence, LLC. Lack of Standards. W(il d ) W(ild ) W(est ) of Sensors Partial Standards/Record Layouts Requirements Provision Configuration Remote Management/Field Upgrades Sensor Data Template

erling
Download Presentation

Solving the Back End with Platform Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Solving the Back End with Platform Solutions Alex Vishnev CTO Global Convergence, LLC.

  2. Lack of Standards • W(ild) W(ild) W(est) of Sensors • Partial Standards/Record Layouts • Requirements • Provision • Configuration • Remote Management/Field Upgrades • Sensor Data • Template • Unit Identification • Date/Time of the Event • Event Code • Event Data

  3. Platform Issues • Adaptation • Protocols – Moving Target • Quickly/Efficiently Deal with New Sensors • Scalability • Scalability and Redundancy • In-house or Cloud Based Solutions • Service Provision • Automatic OTA Configuration/Upgrades • Manual (Fulfillment Configuration Steps) - Temporary • Business Continuity • Adding/Changing Sensors • Maintaining Business Rules • RMA Logistics • Billing • Customer Identification • Service Association • Audit/Accounting/Tracking

  4. Sensor Adaptation • Communications Adaptors • Polling/Pushing • SMS/GPRS/Others • One-Way/Bi-Directional • Customize/Parameterize Sensor Specific Operations • Sensor Configuration • Default • Groups • Sensor Specific Parameters • Customer/Service Specific Parameters • Firmware Upgrades • Sensor Data Templates • Incoming Records Layout • Data Normalization • Map Sensor Specific Data Elements to Known System Elements

  5. Platform Scalability • Number of Devices • Bandwidth Utilization • Event Processing • Architecture Options • Load Balancers • HA Pairs • Hot Stand-by • Geographic Redundancy/Multi-Site • In-House Data Centers/”Cloud” Providers (Amazon, Rackspace, etc)

  6. Service Provisioning • Service to Sensor is 1:M • Identifying Each Sensor in a Service • Creating Sensor Configuration • Logistics • Shipment From Different Vendors • Consider Fulfillment House (BrightStar, Amazon, etc) • OTA Configuration Process • Many Different Approaches • Simplify OTA Configuration/Upgrade via Customized Script • Expect/Send State Diagram • Manual Configuration (Temporary Solution) • Time Consuming • Error Prone • Not a Permanent Solution

  7. Business Continuity • NO-Nos • Bundle Business Logic with Specific Sensor • Assume Single Sensor • Single Service/Offering • Always Free Service • Sensor is “immortal”

  8. Billing • Correlate Event to Service • Sensor Identification • Customer Identification • Service Profile • Policy (Charge, Track, etc) • Create Event Records • Account/Audit • Tracking • Billing Mediation

  9. Thank YouAlex VishnevCTOGlobal Convergence, LLCavishnev@newglobalconvergence.com704-360-0351

More Related