Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
149
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SQGO INTELLECTUAL PROPERTY BASIC TECHNICAL OVERVIEW
  • 2. DISCLAIMER
    • This presentation is not a commercial product presentation and does not outline specific problems solved or exact value propositions delivered by SQGO products.
    • This presentation covers, from a simplified academic perspective, general wireless industry problems and how patents filed by SQGO will solve these problems.
  • 3. AGENDA
    • Problems
    • Solutions
    • Benefits
    • Technical Details
  • 4. INDUSTRY PROBLEMS
    • Inconsistent look and feel of applications.
    • Multiple platforms to develop for.
    • Multiple carrier approvals needed for distribution.
    • Multiple carrier revenue/fee models.
    • Application security.
    • Bandwidth scarcity and cost.
    • Physical distribution of applications to user devices.
    • Battery power consumption
  • 5. EVERY PLATFORM IS DIFFERENT
    • 80% of developer work is not focused on business logic.
    • Every platform requires replication of work.
    • A matrix of platform APIs and platform specific code generates inconsistencies, errors and security holes.
  • 6. SOLUTION
  • 7. SQGO COLLAPSES THE PLATFORM MATRIX
    • SQGO supplies a strong application container/socket for each platform creating a secure “abstraction layer” and a “work equalizer” for developers.
    • Novel use of the socket generates multiple benefits.
  • 8. BENEFITS
    • Less Effort
    • Consistency
    • Pre-approval & Negotiated Fees
    • Security
    • Network and Battery Efficiency
    • Network Flexibility
    • Physical Distribution
    • Lower Development Costs
  • 9.  
  • 10. BENEFIT: LESS EFFORT
    • One development effort enables:
      • cross-platform execution
      • cross-carrier distribution
  • 11. BENEFIT: CONSISTENCY
    • Write once, deploy everywhere, always behave identically on every platform.
    • The SQGO application interface is one of the bounding characteristics of the socket.
    • Only pre-defined behavior, including application look and feel, is permitted by the socket - thus guaranteeing consistency.
  • 12. BENEFIT: PRE APPROVAL & NEGOTIATED FEES
    • SQGO ensures the application socket is pre-approved by carriers as secure.
      • applications can then be delivered/ provisioned to the socket without carrier approval.
    • Provisioning charges and utilization fees are pre-negotiated with carriers by SQGO.
    • SQGO acts as a clearinghouse for “reverse billing” of associated charges.
    • Charges can be equalized across carriers.
  • 13. BENEFIT: SECURITY
    • Applications can only securely behave or have a state that is “allowed” by the socket, everything else can be discarded.
    • Platform API’s and other resources are only accessible via security-signed behavior.
    • Network communication is as secure as the wireless network security layers available.
    • “ Intermediate form” allows for multiple verifications before work is done.
  • 14. BENEFIT: NETWORK EFFICIENCY
    • Application descriptions in the form of uniform hierarchical data (XML) are initially fed to the application socket.
    • The XML can be generated and manipulated solely on the device or a remote server or a combination of device and server.
    • Only target sections of cached XML (application segments) need to be updated when the application is modified or engaged.
    • Network communication form is compact.
    • Methods conserve power.
  • 15. BENEFIT: NETWORK FLEXIBILITY
    • Application code can easily be distributed between device and server.
    • Since applications are stored as trees, applications may be incrementally updated.
    • Developer does not have to perform work to make an application “network aware”.
    • Running code may be migrated from device-to-device (easy to say, but normally very difficult to do!).
  • 16. BENEFIT: PHYSICAL DISTRIBUTION
    • The end-user facing “skin” of the socket provides search, directory and application management functions. Similar to a “finder” or “launcher”,
    • SQGO applications or application segments can also be messaged to users using carrier supported MMS infrastructure.
    • Applications may be exchanged through Bluetooth, 802.11b, and other wireless protocols.
  • 17. BENEFIT: LOWER DEVELOPMENT COSTS
    • Simplicity of application model enables developer to operate easy-to-use visual tools to create many applications without coding.
    • Coding model is based around familiar XSLT metaphors.
    • Easy to consistently emulate.
  • 18. ARCHITECTURAL DETAILS
  • 19. KEY REVELATION: XML IS OUR METAPHOR
    • Organize every part of an application as an XML tree.
      • User Experience
      • Code
      • “State” (where we are)
      • Media
    • Update the tree automatically when the user interacts with the application.
    • Let the application perform operations on the device exclusively through the tree.
    • Holds all of the state assumptions between the application and the operating system.
  • 20. EVOLUTION IN CLIENT PROGRAMMING Development Time Traditional Simple Quick GO Platform Proxy Windows CE Java Palm OS Brew XML Code SQGO Platforms (BREW, JAVA, PALM, CE, etc) API Developer work (HEAVY LIFTING) for desired user interface, communication and I/O Application Logic SQGO PLATFORM PROXY LAYER (RED) HEAVY LIFTING IS DONE FOR DEVELOPER! API API API API
  • 21. EQUALIZING CLIENT ARCHITECTURES
  • 22. XML SUPERSTRUCTURE APPLICATIONS
    • Entire programming model based on XML structures.
    • XML not just a document, but a metaphor.
    • Perfect blend of document and application programming models.
      • code = transformations
      • network communication = application “snippets”
      • data structures = XML tree
      • API defined by organization, not toolkit
  • 23. DESIGN FEATURES
    • Easy To Program
    • Small Code Sizes
    • Novel Network communication model
    • Superstructure allows security verification
    • No API assumptions within XML code
    • Easy migration path
      • SimpleOS as a UI shell
      • SimpleOS takes over client
    • UI an OS tightly tied together
  • 24. VALUE PROPOSITION