Category: Technology Licenses
Created On: 2022-04-28
Record Count: 5
- Telecommunications Equip
- Media & Entertainment
- Broadcasting/Cable TV
- Telecommunications Svcs & Equip
- Computers & Office Equipment
IPSCIO Report Record List
Below you will find the records curated into this collection. This summary includes the complete licensed property description so that you can review and determine if this collection covers the topics, technology or transaction type that is relevant for your needs. The full report will include all relevant deal data such as the royalty base, agreement date, term description, royalty rates and other deal terms. For reference, here is a sample of a full IPSCIO curated royalty rate report: Sample Report
IPSCIO Record ID: 5367
1. I-IP/950289 Low-Bandwidth Network Window System. Mike Dixon, Pavel Curtis, David Nichols, John Lamping.
2. F-IP/950990 Jupiter Audio/Video Architecture Secure Multimedia in Network Places. Pavel Curtis, Mike Dixon, Ron Frederick David Nichols.
3. A-IP/951514 Automated Access to Expertise. Richard Bruce, David Nichols, Danny Bobrow, David Goldberg.
4. F-IP/921756, Software Video Compression for Teleconferencing, Ron Frederick.
1) Java, C, and C++ 'placeware' source code, providing shared Java applications over a network in a web browser, with audio communications between participants. This includes, without limitation, the code developed by _________, _________, ___________, __________, and ____________ during calendar year 1996 and third parties working with those developers.
2) C++ source code to implement video send/receive capability for the Microsoft Windows version of the Jupiter client. This includes, without limitation, code developed during 1995.
3) Developer's Guide, Administrator's Guide and API Reference Documentation relating to the above.
Licensee is a leading provider of services and products that enable businesses to conduct real-time, interactive meetings and presentations, or web conferences, over the Internet.
IPSCIO Record ID: 29015
Technology shall mean the eViewMediaEngine which is owned by Licensor and protected by USA Patent numbers 7,003,168, 6,711,299 and 6,904,175.
The technology provides APIs to control the processes of uploading the ME format media into an archive that supports media distribution and rendering. The underlying engine components reside in both the execution time client and server(s). The archive structure supports maintaining more than one copy of an object for both redundancy and for load sharing considerations. Each archive object in the ME format has, as a minimum
â€¢ Video index file(s)
â€¢ Video data file(s)
â€¢ Audio index file(s)
â€¢ Audio data file(s)
Within the scope of this agreement, it is understood that the ME format will be extended to include
â€¢ Script index file(s)
â€¢ Script data file(s)
The archive will also be extended to support the Asier encryption model.
â€¢ Access the index and data files from an archive
â€¢ Buffer the video object such that the video starts to play quickly (typically within 3 seconds), but can sustain interruptions in the flow of data from the server.
â€¢ Manage the overall processor and bandwidth constraints. The player supports bandwidth coordination among the videos that are playing simultaneously. Each video can be designated as â€œprimaryâ€ or â€œsecondaryâ€. When initial buffering occurs, primaries are able to get to the initial fast start state (3 seconds worth of render time) before a secondary may start. At any time while playing/buffering, the secondary(s) will back off if a primary is about to stall for lack of data. Any video may have its buffering bandwidth effect controlled to a percentage of its computed average bandwidth requirement (i.e., a video may be loaded at 110% of its average bit rate rather than loading as fast as it can – ME supports both paradigms).
â€¢ Start a video on any designated frame. The player supports an API that includes a request to play from frame(x) to frame(y) and/or start playing to end at frame(x). This is used to effect slider drag operations that allow the subscriber to advance or backup to any position within a movie with no dependence on prior buffering.
â€¢ Render the video from an internal memory cache. The video is buffered from a stream and is not stored on the local disk. Thus, a two hour movie is never completely contained within the client machine.
â€¢ Support a coordinated actor/director rendering paradigm. Each video rendered on the web page is represented by a Java actor. The page also contains, in this paradigm, a Java director that controls everything visualized by the actor(s) on the page. The director contains a context for each video being managed by it. At any instant in time, an actor is associated (receiving rendering data) with one context within the director. The director may have more contexts than actors in order to buffer video data before it is needed. The contexts may be programmed to trigger events when they get to certain states (i.e., when playing a particular frame, when there is enough data buffered to safely play, when the user clicks on an actor associated with the context, etc.). Each context also supports a complete API control mechanism. The combination of the event architecture and the API allows the context events to trigger control actions in other contexts. This supports a high degree of coordination between videos on the page. As a video plays to certain frames (arrives at certain scenes), another video (or image) on the page may be triggered to take an action.
â€¢ Automatically recover from server disconnects. When connected to a web server to pull the video data, the player will encounter frequent disconnects during the course of a two hour period. The technology supports automatically detecting that this has occurred and to reconnect before the object buffer is drained.
â€¢ Automatically select from multiple object formats. Any ME archive object may be represented in more than one format (resolution, frame rate, etc.). The player environment is capable of analyzing the processor speed and available bandwidth and selecting an appropriate format. The player may also be directed to select or change formats while playing and not be required to start over.
â€¢ Restrict access to the video. The Java player is restricted to operation within a specific web domain. If a different web page tries to activate a player not authorized for it, the player will fail to run. It is understood that under this agreement, this security model will be extended to support the Asier encryption model.
â€¢ Support complex ME formats. The complex ME object format is structurally the same, but supports dynamic frame rate and resolution settings. The video may use a different frame rate for each included scene.
The technology provides a comprehensive solution for live video chat. The chat architecture includes a client API that supports
â€¢ Connecting the client to a VXN server. This operation results in an internal endpoint or IP address that is used to route data from one chat client to another.
â€¢ Enabling local camera capture. The video from the camera is automatically made available to the internal chat architecture for both local display and transmission to the server for use in the chat conference.
â€¢ Making a call. The API allows the local client to make a call through the VXN connection to anyone connected to the VXN by referencing the destinationâ€™s endpoint address. After the appropriate handshake, this will cause the local clientâ€™s audio and video to be transmitted to the destination.
â€¢ Making multiparty calls. The technology supports up to an 8 party call, depending on available bandwidth.
â€¢ Controlling call parameters. The API supports controlling parameters that affect the destinationâ€™s user experience and the bandwidth usage for both parties. These include resolution, frame rate, and quality settings. Most parameters can be changed mid-call.
â€¢ Making audio only calls.
â€¢ Interoperation with H.323 devices.
The technology consists of a combination of source and object (executable) code and associated documentation
â€¢ ME encoder Windows dynamic link library executables
â€¢ ME encoder controller Java applet executable
â€¢ ME player Java applet executable
â€¢ ME upload applet executable
â€¢ ME installer applet executable
â€¢ ME chat installer executable
â€¢ ME chat engine Java applet executable
â€¢ ME chat engine Windows dynamic link library executables
â€¢ ME media engine hosting service PHP executable (obfuscated source code)
IPSCIO Record ID: 3419
The Agreements have a five year term and are non-cancelable except for material default by either party. The Agreements also convey to the Licensee a non-exclusive world-wide License to our patent portfolio existing at the time of the Agreements and for all subsequent patents issued with an effective filing date of up to five years from the date of the Agreements.
In general, patents relate to networked real-time conferencing related technology. Patent numbers include 7,398,296; 7,206,809; 7,185,054; 7,152,093; 7,054,904; 6,972,786; 6,959,322; 6,816,904; 6,789,105; 6,594,688; 6,583,806; 6,437,818; 6,426,769; 6,351,762; 6,343,314; 6,237,025; 6,212,547; 6,081,291; 5,978,835; 5,915,091; 5,896,500; 5,884,039; 5,867,654; 5,854,893; 5,802,294; 5,758,079; 5,751,338; 5,689,641; 5,617,539.
â€œNodeâ€ means a single computing device, such as a hardware server.
â€œSession Initiation Protocolâ€ (â€œSIPâ€) means a signalling protocol, widely used for setting up and tearing down multimedia communication sessions such as voice and video calls over the Internet.
â€œMultipoint Control Unitâ€ (â€œMCUâ€) means an endpoint on the local area network that provides the capability for three (3) or more terminals and gateways to participate in a multipoint conference.
â€œVirtual Private Networkâ€ (â€œVPNâ€) means a computer network in which some of the links between nodes are carried by open connections or virtual circuits in some larger network (e.g., the Internet) instead of by physical wires.
IPSCIO Record ID: 6949
The Technology is the software application known as â€œTiny Web Serverâ€ including any derivative works. This Technology is written in C, approximately 3600 lines of source code, and its source code is named â€œwebsrv.câ€. It is a fully functional web server software that occupies very little memory. Its executable code is approximately 100K bytes, which makes it a good fit in a mobile internet device.
IPSCIO Record ID: 28948
The associated license agreement provides the right for Licensee and its Affiliates to use the Deliverables owned or controlled by Licensor. Products will be exclusively commercialized, sold or otherwise disposed, directly or indirectly by Licensee and/or its Affiliates in the Exclusive Market. The MTA-1 Project Exclusive Market shall mean the market relative to voice over IP applications for consumer terminals over hybrid fiber coax cable television networks.