Royalty Report: Telecommunications Equip, Consumer Electronics, Media & Entertainment – Collection: 26425

License Grant

The Company has a royalty agreement with the original design firm for patent for the FlexCam; electronic camera technology.

License Property

FlexCam is a very small color video camera and microphone attached to a 3/8ths inch flexible 18- inch shaft which transmits live video images of persons, objects or documents to a monitor or through a separate video-capture board to the monitor of a computer.

Field of Use

The Company designs and manufactures image capture, transmission and manipulation devices for use as components of systems for security, medical, desktop computer video applications, video-teleconferencing and computer-based and non-computer based audio-visual presentations.

License Grant

Licensor, an entity controlled by an officer and stockholder of the Licensee, hereby grants to Licensee during the Term (as such word is defined in Section 12 of this Agreement), unless earlier terminated as described in Section 13. an exclusive, royalty bearing license in the Territory to receive and utilize the Technology and Developments, and to practice the inventions disclosed in any and all Licensed Patent Rights, Technology, and Developments for the purpose of making, using, selling, importing and offering for sale the Licensed Products in the Territory, and having any of the foregoing actions taken (the 'License').

License Property

LICENSED PATENT RIGHTS
Serial No.

Filing Date

Title

08/708,044

Aug. 30, 1996

Surgical/Diagnostic Imaging Device/Non-Medical Only

PCT/US96/14921

Sept. 16, 1998

Surgical/Diagnostic Imaging Device/Non-Medical Only

08/730,089

Oct 15, 1996

Video Gynecological Examination Apparatus/Non-Medical Only

PCT/US97/01900

Feb. 6,1997

Video Gynecological Examination Apparatus/Non-Medical Only

08/753,013

Oct 22, 1996

System for Single-Puncture Endoscopic Surgeiy/Non-Medical Only

PCT/US97/1899

Feb. 6,1997

System for Single-Puncture Endoscopic Surgery/Non-Medical Only

60/045,817

May 7, 1997

Device for Coupling A CCD Camera to An Endoscope/Non-Medical Only

Inventor: Robert Lee Thompson (provisional)

60/054197 to 450/7000

July 30, 1997

Aircraft Monitoring System

60/054198 to 450/7001

July 30,1997

Video Scope

60/057057 to 450/7002

August 27, 1997

Hydro Cam (Flex Cam)

60/056209 1253/7000

August 21,1997

Remote Control Touch Pad for surgical/diagnostic imaging device (provisional)

Field of Use

Licensee desires to acquire, from Licensor, an exclusive worldwide royalty bearing license to make, use, develop, import, sell and offer certain non-medical products, as hereinafter defined; and Licensor has agreed to license the certain non-medical products on the terms and conditions contained in this Agreement.

The Licensee designs, manufactures and markets ruggedized camera systems for tactical use by military, paramilitary, law enforcement, public safety, and security personnel.  By definition, ruggedized  systems can withstand violent shock and vibration while operating in extremely harsh climatic conditions.  To be defined as a “ruggedized camera”, equipment must achieve military’s MIL-STD-901D Grade “A” Shock Certification.

License Grant

Licensor wishes to grant the Licensee the worldwide exclusive right to sell, assign, and transfer all of its right, title and interest in any inventions related to the Patents to the Licensee;  including the exclusive right to sublicense.

License Property

This technology is remote, real time two-way audio with video communication, which incorporates a camera, built-in Web server and network interface.  The technology will manage areas of importance independently by providing programmable audio or by alerting designated users via an audio/video transmission to a smart phone or other compatible device.

Field of Use

Licensee wishes to engage in the business of developing as well as marketing products and services protected by the Patents.

License Grant

The Licensor hereby grants to British Licensee, a license to use, sell and sublicense the Technology within the Territory as is or as a derivative work embedded in the Licensee's products.

License Property

Licensor has a comprehensive video platform for real-time integration, delivery and archiving of live and streaming interactive media.  Licensor solution is perfect for broadband service providers seeking a ubiquitous platform for multiple services, and service companies seeking the fastest, most robust platform for live video services.

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.

Video Archive
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.

Video Distribution
The technology provides APIs to control access to objects in the video archive, supporting object rendering in a web distribution model. There is an underlying Java based player that supports rendering multiple videos simultaneously on an HTML web page with programmable coordination among the videos. The player and its supporting Javascript environment have all of the elements required to:

• 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.

Video Chat
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 service controller JavaScript source code

• ME media engine hosting service PHP executable (obfuscated source code)

Field of Use

The rights granted apply to the platform for live video services.