Comcast Residential Services Gateway
`RFI Response
`29 March 2002
`
`
`BeComm corporation™
`4148B 148th Avenue NE l Redmond WA l 98052
`
`TELEPHONE
` 425.458.4439
`FACSIMILLE
` 425.458.4442
` www.becomm.com
`
`Page 1 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`Table of Contents
`1 Overview ..................................................................................................................... 4
`1.1 Document Overview .......................................................................................................... 4
`1.2 BeComm Overview ............................................................................................................ 4
`1.2.1 Products & Services ................................................................................................................ 5
`1.2.2 Relevant Experience ............................................................................................................... 9
`1.3 Solutions ............................................................................................................................. 9
`1.4 UI and Hardware Explorations ........................................................................................ 10
`2 Overall System Architecture ................................................................................... 12
`2.1 Hardware and Firmware ................................................................................................... 14
`2.1.1 Processor Core ...................................................................................................................... 15
`2.1.2 Power Supply ........................................................................................................................ 16
`2.1.3 DOCSIS 1.1 Modem ............................................................................................................. 16
`2.1.4 Ethernet ................................................................................................................................. 17
`2.1.5 USB ....................................................................................................................................... 17
`2.1.6 Serial Interfaces .................................................................................................................... 17
`2.1.7 Memory Expansion ............................................................................................................... 17
`2.1.8 Battery Backup and Operation .............................................................................................. 17
`2.1.9 RF .......................................................................................................................................... 18
`2.1.10 PLC – High Speed ................................................................................................................ 19
`2.1.11 Home PNA ............................................................................................................................ 19
`2.1.12 Serial Expansion ................................................................................................................... 19
`2.2 Physical Design Requirements (sect. 2.2.1 – 2.2.6) ......................................................... 19
`2.3 Application Interface ........................................................................................................ 20
`2.3.1 Application Categories ......................................................................................................... 20
`2.3.2 Application Programmer Interface (API) ............................................................................. 21
`2.4 Remote Management Services ......................................................................................... 22
`2.4.1 Health Status ......................................................................................................................... 22
`2.4.2 Software Upgrades ................................................................................................................ 23
`2.4.3 Diagnostics ............................................................................................................................ 23
`2.4.4 Logging ................................................................................................................................. 24
`2.4.5 Access and Service Usage .................................................................................................... 24
`2.4.6 Security ................................................................................................................................. 24
`2.4.7 Console Password ................................................................................................................. 24
`3 Vendor Questions (Section 3 of RFI) ...................................................................... 25
`3.1 Questions Common to All Vendor Categories ................................................................ 25
`3.1.1 Standards Compliance & Licensing ..................................................................................... 25
`3.1.2 Support .................................................................................................................................. 26
`3.1.3 Development & Business Planning ...................................................................................... 26
`
`29 March 2002
`
`BeComm Confidential
`
`Page 2 of 29
`
`Page 2 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`4 Supporting Documentation ..................................................................................... 28
`4.1 BeComm Corporation ...................................................................................................... 28
`4.1.1 Product Datasheets ................................................................................................................ 28
`4.1.2 Hardware Explorations ......................................................................................................... 28
`4.1.3 White Papers ......................................................................................................................... 28
`4.1.4 Architecture Drawings & Specifications .............................................................................. 28
`Integration Partners .......................................................................................................... 28
`4.2.1 Wind River Systems ............................................................................................................. 28
`4.2.2 Bsquare Corporation ............................................................................................................. 29
`4.2.3 Wipro Technologies .............................................................................................................. 29
`
`4.2
`
`
`
`29 March 2002
`
`BeComm Confidential
`
`Page 3 of 29
`
`Page 3 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`1 Overview
`1.1 Document Overview
`This document is meant to serve as a response to Comcast’s “Residential Services
`Gateway Request for Information”. The focus of the document is on how BeComm’s
`communications platform, Strings, and BeComm’s network application SDK, the
`RADkit, can be used to create a platform for residential gateways and other network
`devices.
`To this end, the framework described in this document illustrates how a network operator
`such as Comcast can use BeComm technology to create managed, semi-open networks
`that spur the creation of innovative applications and the adoption of new media services
`within the home.
`As a software vendor, BeComm products and technologies are all designed to be
`hardware, operating system and network independent. Strings and the RADkit are
`available on most 32-bit operating systems and chip sets and also support development in
`a wide variety of programming languages1. This level of portability provides operators
`complete flexibility in deciding on hardware and operating system. The decision to use
`Strings and the RADkit is therefore largely independent of the underlying hardware and
`operating system selected for a given solution.
`This response is also backed by the support of our world-class service partners who
`provide BeComm with a wealth of engineering services, technologies, solutions, and
`platform integration. Each of our partners can provide application and system level
`integration services for Strings enabled systems. Several of our partners, including
`Bsquare and Wind River Systems, also provide extensive hardware engineering and
`design services that can be leveraged to quickly bring Strings solutions to market.
`Included you will find additional information on our service partners including datasheets
`and specifications on relevant offerings.
`The following sections are included in this document:
`1. BeComm Overview: an overview of BeComm Corporation and its related
`products, services, partners and solutions.
`2. Overall System Architecture: A detailed description of the overall system
`architecture of a Strings enabled RSG solution.
`3. Vendor Questions: Responses to Comcast RSG technical requirements and
`Comcast Vendor Questions.
`4. Supporting Documentation: supporting documentation on BeComm and our
`integration partners.
`1.2 BeComm Overview
`Founded in 1996 and based in Redmond, Washington, BeComm is a privately held
`company that provides software platforms and tools that enable Operators, OEMs and
`ISVs to build innovative applications for today’s highly networked world. BeComm
`products provide a complete framework for the rapid development, deployment and
`management of applications that efficiently share content, media, devices, and resources
`
`1 See included Strings and RADkit datasheets for list of available operating systems, chipsets and languages.
`
`29 March 2002
`
`BeComm Confidential
`
`Page 4 of 29
`
`Page 4 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`in heterogeneous networked environments. By significantly reducing the complexity and
`cost to build these applications, BeComm enables customers to bring cost effective
`applications to market that drive increased revenue and provide unparalleled value.
`
`1.2.1 Products & Services
`
`
`1.2.1.1.1 Strings™ - A Platform for Managed Network Applications™
`Strings is a platform independent software engine that enables unprecedented access to
`network data, content, services, and other devices, independent of operating system,
`network, or application. Strings sits between applications and underlying operating
`systems and facilitates the routing, transformation, and delivery of data to and from
`resources in heterogeneous networks. Strings provides a framework for creating an
`entirely new breed of extremely lightweight, powerful, and managed network
`applications. With its advanced data shaping capabilities, namespace management and
`Rules-based Mapping engine for dataflow management, Strings enables the rapid
`deployment of applications in heterogeneous networks without the typical application
`complexity or compromise in network service.
`
`1.2.1.1.2 Beads™
`Beads are highly modular software libraries that can be recombined at runtime by Strings
`to manage dataflow through a system. Beads provide a myriad of services from
`wrapping underlying operating system services and hardware resources to implementing
`network protocols and multimedia codecs.
`Since Beads can encapsulate underlying OS services and hardware resources in a manner
`that provides complete separation and runtime reusability of the service, Strings can
`effectively re-map these services in any combination and order. This dynamic Mapping
`capability provides Strings with unprecedented flexibility in managing dataflow through
`the system and enables applications to seamlessly leverage end-to-end system services
`both locally and remotely in the network.
`BeComm has developed several hundred Beads to date and in conjunction with our Bead
`development partners Wind River, Bsquare and Wipro we are able to provide new Beads
`to meet virtually any customer requirement.
`For more information on Strings please see “Using Strings to Compose Applications
`form Reusable Components” and “Strings – A Technical Overview”.
`
`1.2.1.1.3 Features
`• Path-based Architecture:
`Strings features a patent-pending Path-based architecture that facilitates highly-
`efficient dataflow management through a system. This architecture also allows Strings
`
`29 March 2002
`
`BeComm Confidential
`
`Page 5 of 29
`
`Page 5 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`to apply QoS across all services that are mapped onto a given dataflow. This level of
`fine-grained QoS management avoids common problems such as priority inversion2
`• Mapping Engine:
`Strings dynamically maps an optimal set of Beads onto dataflows in the system. This
`ensures maximum network and system efficiency. This Mapping capability also allows
`Strings to facilitate interaction with network resources without exposing the interfaces
`and media requirements of those resources to application developers. Strings enabled
`RSGs can leverage this capability to serve as protocol gateways that bridge disparate,
`heterogeneous networks and resources into a common global namespace.
`• Rules Database:
`The Mapping capability in Strings is augmented with a Rules database that allows
`system administrators to specify the exact set of system services (Beads) that should
`be applied to a given dataflow type. Rules can applied based on a variety of system,
`network or resource based attributes. Examples of attributes include available
`memory, network bandwidth, content-type, user-profile or service type.
`• Namespace:
`Strings maintains an active repository of named objects in the Strings Namespace.
`Any resource that can be encapsulated as an object can be populated in the
`Namespace. Examples include:
`§ Devices such as speakers, microphones, tuners
`§ Variables such as available memory, time of day, cpu utilization
`§ Files
`§ Dataflows (see section on dataflows below)
`§ Objects registered by RAD applications
`Every Strings enabled system maintains a local copy of its Namespace. These
`Namespaces are in turn synchronized through a patent-pending discovery protocol that
`enables every Strings device to have the same view of a global network Namespace.
`Objects can be populated in the Strings Namespace by a variety of Namespace
`providers including network discovery services such as UPnP, HAVi, Bluetooth and
`Jini. Once objects are in the Namespace, the actual protocol requirements of
`communicating with the objects are abstracted from services that interact with the
`object. In addition any Strings device with multiple network interfaces can serve as a
`Namespace gateway facilitating the bridging of Namespace information from one
`network to another.
`
`
`
`2 Traditional operating systems use common queues to manage incoming network packets. This causes low priority
`packets such as email and chat to interfere with higher priority packets such as voice and video. The resultant
`priority inversion causes poor performance and unpredictable behavior.
`
`29 March 2002
`
`BeComm Confidential
`
`Page 6 of 29
`
`Page 6 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`• Platform Neutrality:
`The Strings runtime is built on top of a thin operating system abstraction layer that
`facilitates portability across virtually any 32-bit operating system and chip set. Strings
`has a built in scheduler for managing dataflows and does not depend on the underlying
`OS for scheduling. This ensures that services deployed on Strings behave consistently
`regardless of what OS they are deployed on. The Strings scheduler has been highly
`optimized for dataflow management and enables direct Mapping of QoS primitives to
`dataflows.
`
`1.2.1.2 RADkit™ - The fastest way to build powerful network applications™
`The RADkit is the first toolkit of its kind designed specifically to build media-rich
`applications for networks. From peer-to-peer applications to distributed multimedia
`solutions that ship audio and video through a network, the RADkit™ makes it possible to
`build network applications in far less time and with far greater functionality that ever
`before. The RADkit™ provides everything application developers need to build
`applications that interact with network resources, content, data, and other network
`devices through simple interfaces that are accessible from Java, ActiveX, and C++. And
`because the RADkit uses the power of Strings, OEMs and ISVs can create managed
`platforms that enable developers to rapidly build innovative applications that increase the
`velocity of content™ and ultimately generate more revenue.
`Features:
`• Browse: the browse class allows applications to query the local Strings Namespace
`for network objects based on attributes. Since every Namespace is updated to reflect
`objects available in all visible networks, applications can use the Browse class to
`seamlessly identify resources across heterogeneous networks.
`• Network Object: The network object class allows applications to invoke methods on
`objects discovered through the Browse class. Applications can control any network
`object without requiring the location, interface or protocol requirements of the object.
`• Dataflow: In addition to controlling network objects, applications can create
`dataflows from source objects to one or more sink objects. This service can be used to
`route media throughout the network. Dataflows to more than one sink object can be
`synchronized even over unreliable networks3.
`• Event: Applications can register for notifications on events that occur locally or
`throughout the network. Since Strings serves as a protocol broker in heterogeneous
`environments, applications can register for events independent of the underlying
`network event protocols4.
`
`
`3 This service is very useful in routing content such as movie content where the audio is intended for one network
`device such as a smart stereo and the video for another device such as a wireless tablet. It is also very useful for
`local movie playback as the synchronization capability ensures proper playback even under system load.
`4 Most discovery services such as UPnP, HAVi and Jini specify competing and non-compatible event mechanisms.
`By using the RADkit for event notification, applications are hidden from the underlying protocol requirements of
`event systems.
`
`29 March 2002
`
`BeComm Confidential
`
`Page 7 of 29
`
`Page 7 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`1.2.1.3 RADteams™ - Custom solutions from the experts in distributed systems
`With over 6 years of research and development expertise, world class partners and proven
`commercial solutions, BeComm’s RADteams help operators, OEMs and ISVs bring
`Strings and RADkit based products to market quickly and effectively. RADteams provide
`a full-spectrum of engineering support, including application development, system design
`and architecture consulting. Our industry leading partners, Wind River Systems, Bsquare,
`Wipro, Frog Design and Stratos enable us to pull together the right partners, platforms
`and technologies for virtually any solution.
`Whether the requirement is for a completely out sourced turnkey solution including
`hardware and software designs or architecture analysis and support, customers can
`leverage BeComm’s industry proven expertise and industry leading partners to cost
`effectively bring innovative Strings and RADkit based solutions to market.
`Partner Overview
`Wind River Systems: BeComm has partnered with Wind River Services, a division of
`Wind River Systems to provide customers with world-class integration and development
`services on VxWorks hosted solution. Wind River has extensive experience as a Strings
`platform
`integration partner, Bead development partner and RAD application
`development partner. In addition our partnership with Wind River Systems allows us to
`leverage their in house Doctor Design services team which is capable of providing a
`wealth of industrial, mechanical and electrical engineering service. Wind River and
`BeComm have co-developed several reference solutions including residential gateway
`systems and wireless tablets. In addition, both companies have invested significant
`resources in optimizing the performance of Strings on VxWorks based systems.
`http://www.windriver.com
`
`Bsquare Corporation: BeComm has partnered with Bsquare Corporation to provide
`customers with complete support for Strings based solutions on Windows CE and
`embedded Windows NT/XP. Bsquare can serve as a Strings platform integration partner,
`Bead development partner and a RAD application development partner. Bsquare also
`provides a variety of hardware related services including their SmartBuild (see attached
`datasheet) solutions, which enable rapid configuration and deployment of Windows CE
`solutions on target platforms. Bsquare also provides production ready hardware systems
`for OEMs looking for the fastest possible access to emerging markets. Bsquare and
`BeComm are in the process of co-developing several reference solutions including media
`servers, wireless tablets and networked audio adapters. http://www.bsquare.com.
`Wipro Technologies: Wipro is the world’s first SEI CMM Level 5 certified software
`services company. They provide a wealth of engineering services as well as several pre-
`packaged product solutions. Wipro has partnered with BeComm to provide Strings
`platform
`integration services, Bead development services and RAD application
`development services. Our relationship with Wipro provides us with access to a highly
`skilled, world-class engineering services company that we can leverage to help customers
`bring Strings enabled solutions
`to market across a variety of platforms.
`http://www.wipro.com.
`
`29 March 2002
`
`BeComm Confidential
`
`Page 8 of 29
`
`Page 8 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`Figure 1 - Intel Web Tablet
`
`1.2.2 Relevant Experience
`1.3 Solutions
`In addition to the RADkit, developers can leverage pre-packaged solutions offered by
`BeComm to accelerate time to market for new products. A sample of these solutions is
`offered below5:
`Wireless Tablets: The Intel® Web Tablet was
`built with Strings to manage and deliver rich
`digital audio content. With Strings, users can
`enjoy digital audio on the tablet by playing files
`stored on their PC, on the Internet or by
`listening to Internet radio from anywhere in the
`home. Strings makes this possible by acting as a
`gateway for streaming audio from the Internet to
`the Web Tablet. With Strings, the Web Tablet is
`able to leverage the PC's processing power and
`memory, so that it can play rich audio content without
`requiring additional processing on the Tablet.
`Not only does this reduce the cost of the Web
`Tablet, but because Strings manages the audio
`streams in real-time, users can experience "live" digital audio, away from the PC, without
`sacrificing performance or sound quality.
`In addition to audio content, BeComm’s tablet solution provides support for telephony,
`remote television viewing, movie playback and remote control.
`Distributed Audio: BeComm’s distributed audio solution provides a complete
`framework for OEMs and ISVs to deliver rich audio content to the home. The distributed
`audio solution allows users to playback rich audio content from PCs and other sources to
`lightweight network enabled adapters. The BeComm solution provides complete PC
`software as well as software that can be deployed on thin network clients such as low-
`cost networked adapters that users can attach to existing stereo equipment. The BeComm
`audio solution is the only solution available today that enables content sharing across
`multiple PCs as well as synchronized playback to multiple clients. This means end-users
`can access audio content even if it is distributed across multiple PCs and they can enjoy
`playback on any audio-capable networked device in their home. The BeComm audio
`solution provides a plug-and-play setup. No IP address configuration, windows file
`sharing or other onerous user configuration is required.
`Media Server: The BeComm Media Server solution provides complete management,
`routing, transformation and delivery of rich-media content to a variety of devices on a
`LAN. This solution enables users to access the content of their choice on the device of
`their choice in the format of their choice. This solution also includes support for multiple
`PIP windows for enhanced TV viewing, web browsing, PVR capabilities, dynamic
`routing of content to other devices such as web tablets and the PC as well as telephony
`support and firewall/NAT services.
`
`
`5 For more information on BeComm solutions, please see attached datasheets included in this document.
`
`29 March 2002
`
`BeComm Confidential
`
`Page 9 of 29
`
`Page 9 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`Telephony Gateway: BeComm’s telephony solution allows outside callers to have their
`phone calls routed to any networked device or analog phone. The solution is based on
`BeComm developed Voice-Over-IP Beads. The solution includes support for voice mail
`with the ability to route voicemail to a network disk or email program, conference
`calling, call forwarding, call transferring and other advanced telephony features. The
`solution can be extended by adding in Beads for Internet content and television access
`which allow users to call in via a standard analog phone and listen to Internet based
`music or radio content and to tune into live TV channels. Other available packages also
`exist to enable complete access to home security and home control through standard
`analog phones. Access to any other Strings enabled devices on the LAN is seamlessly
`available. This is solution is highly suited to any SOHO or residential environment and
`can be added to any system running Strings with POTS access.
`IP Router/NAT/Bridge: Strings based IP routers, NATs and bridges provided highly
`scalable and predictable systems. Because of the efficiencies in Strings, these solutions
`can take advantage of QoS directives or application layer intelligence to selectively apply
`QoS to routes. These packages require no additional code beyond our core TCP/UDP/IP
`Beads since IP routing, NAT, and bridge functionality can be completely expressed in
`Rules that are loaded into the Strings Rules database.
`Extended-PC: BeComm has led the industry in research on extended PC solutions.
`Strings is available for all flavors of Windows and Linux giving users ubiquitous support
`for enabling their desktop systems with Strings. Adding Strings to a PC turns an ordinary
`PC into a distributed source of network resources such as processing power, application
`services, operating system services, peripherals and content. These services are in turn
`seamlessly available to all Strings enabled network devices and RAD applications. As a
`result, the Strings enabled PC is a powerful extension of the surrounding network of
`devices and applications. Examples of leveraging the Extended-PC including using the
`PC for decoding of rich media content (see Tablet solution discussed above), using Bead
`wrapped services on the PC such as text-to-speech to offload processing from lightweight
`clients, using the disk of the PC for media storage and accessing content across multiple
`PCs through a single Namespace.
`These applications represent a small sample of the types of applications that can be built
`with Strings. All solutions built using Strings are implicitly interoperable and provide
`seamless sharing of resources. As such, a Strings enabled tablet can control a Strings
`based audio device, a Strings enabled PC can serve as a file store for voice messages
`from a Strings enabled telephony system, a Strings enabled residential gateway can
`provide access to all these services and devices across the home LAN.
`1.4 UI and Hardware Explorations
`In early 2001, BeComm commissioned Frog Design to develop a definitive user interface
`for media services within the home. The UI was designed primarily for television
`viewing but was also suitable for PCs and handhelds. Based on this UI, users can create
`media related activities such as television viewing, web browsing, music listening and
`telephony that span multiple devices in the home network. This would, for example,
`allow a user to watch television with a wireless TV companion and a networked stereo.
`In this case, the UI would direct Strings to route instant replays, EPG information and
`PIP content to the wireless companion while routing the main television picture to the
`
`29 March 2002
`
`BeComm Confidential
`
`Page 10 of 29
`
`Page 10 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`screen of the TV and the audio of the television show to the speakers of the networked
`Stereo.
`The entire UI was developed using Macromedia’s Director tools on the RADapi. The
`fact that the entire TV application was developed with simple UI tools evidences the
`extent to which application development using the RADkit is simplified. A screen shot of
`the UI is included below:
`
`Figure 2 - BeComm's Universal Media Controller
`
`
`
`In addition to these UI explorations, BeComm commissioned Frog to develop hardware
`prototypes for four strategic consumer network appliances: a media TV, a media
`server/gateway, a wireless media tablet and a network media relay for networking legacy
`stereo equipment. Datasheets outlining these four products are included in the supporting
`documentation section.
`
`
`
`
`Figure 3 - BeComm Media Gateway Exploration
`
`29 March 2002
`
`BeComm Confidential
`
`Page 11 of 29
`
`Page 11 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`2 Overall System Architecture
`The diagram below depicts the general architecture of a Strings based Residential
`Gateway6.
`
`Java RADapps
`
`C++ RADapps
`
`MFC/ActiveX
`RADapps
`
`Network Browser
`Class
`
`Dataflow Class
`
`RADapi
`
`Event Class
`
`Netowrk Object Class
`
`Rules Database
`
`Bead Repository
`
`Namespace
`
`Mapping Engine
`
`Path Construction
`
`Scheduler
`
`Operating System Abstraction Layer
`
`Kernel
`
`Object Repository
`
`HomePN
`HomePNA
`A
`
`Bluetoot
`Bluetooth
`h
`
`
`
`802.11b802.11b
`
`
`
`USBUSB
`
`
`
`EthernetEthernet
`
`
`
`DOCSISDOCSIS
`
`Residential Gateway Hardware
`
`
`
`PPPPPP
`
`
`
`ML - PPPML - PPP
`
`
`
`IPoAIPoA
`
`
`
`PPPoEPPPoE
`
`
`
`PPPoAPPPoA
`
`
`
`Protocol FrameworkProtocol Framework
`
`
`
`L2TPL2TP
`
`
`
`IPSecIPSec
`
`
`
`MPoAMPoA
`
`Applications
`
`RAD
`
`RADapi
`
`Strings Runtime
`
`Embedded RTOS
`
`Figure 4 - Strings enabled Residential Services Gateway (note RTOS diagram is based on Wind River
`Systems Tornado for Home Gateways architecture diagram.
`RAD Applications: RAD applicatoins are applications built on top of BeComm’s
`RADapi as provided in the RADkit. Applications outside of the RAD environment are not
`depicted but would interface directly with the underlying RTOS.
`RADapi: The RADapi layer implements a set of application programming interfaces that
`allow applications to interact with the key services that are exposed in the RADapi layer.
`These include a browser service for discovering network objects, a dataflow class for
`
`6 See section 4.3 for additional architecture drawings
`
`29 March 2002
`
`BeComm Confidential
`
`Page 12 of 29
`
`Page 12 of 29
`
`Implicit Exhibit 2039
`Sonos v. Implicit, IPR2018-0766, -0767
`
`

`

`Comcast RFI Response
`
`creating dataflows between objects, an event class for registering for network events and
`a network object class which allows RAD applications to register application level objects
`in the Namespace.
`Strings Runtime: The Strings runtime is made up of services, a Rules database, an object
`resposi