mozi provides a video library for storage of all video content. There are several mecha-nisms that can be used for categorization including hierarchical channels, tags, and cus-tom taxonomies to fit the business need. This content can be surfaced in different chan-nels depending on the customer‘s required layout. The system is divided into front-end and back-end. Standard users would normally only view the front-end, and there are dif-ferent types of roles that can be assigned to users with more access to manage their own, and other people‘s content. User accounts are automatically created on the service when users log in via SAML, and they can have their access level individually upgraded as necessary.
mozi is primarily an internally facing service. Different internal users can be assigned roles that elevate their access level to different parts of the service. These roles include sub-scriber“ to view content, contributor who can submit content but not publish it, editor who can publish content, and administrator who can manage all content and other backend parts of the system. Additionally, a simple Dropbox“ can be exposed to either in-ternal or external users to allow agencies to upload files that are then received by a content manager with one of the above roles. This content manager would then assign metadata and publish the content into the correct channels.
mozi supports ADFS/SAML integration. When a user logs in mozi automatically discovers the user‘s details including email address and AD group membership. As mozi learns these groups they show up in the back-end interface so that they can be used to restrict access to certain content. When a user views a particular channel, content they do not have access to see is automatically screened out. If the user attempts to directly access a video by URL that they do not have access to, they will be blocked. Finally, IP ranges can be specified to completely block the service from certain networks or only allow from cer-tain networks.
mozi uses HTTP Live Streaming technology to dynamically change the video streaming quality for on-demand content based on the available bandwidth to the receiving user. The player constantly monitors the speed of delivery and adjusts the rate up and down depending on performance. The service allows the administrator to set a maximum per-stream bitrate. Video streaming traffic from the mozi service is cachable (but still encrypt-ed) by WAN acceleration devices and HTTP proxy servers.
As above, mozi scales down the quality to a low level if needed, but users on severely constrained networks may still have difficulty receiving content. In these cases we would recommend deploying an HTTP caching solution, or a Peer-to-Peer solution. mozi is compatible with various P2P solutions such as Kontiki and Hive.
mozi uses HLS to dynamically change the video streaming quality based on the available bandwidth. The highest quality experiences can be delivered either with additional hard-ware such as HTTP caching servers (which are likely already deployed) or a peer-to-peer software solution that transparently accelerates the video delivery.
mozi supports embedding videos and other content such as associated comments, ratings and related content in SharePoint pages and other types of website. The SharePoint integration operates without any significant modification to the SP estate. No web parts or SP solutions need to be deployed to enable SP integration. Additionally, mozi supports SharePoint federated search to show video results next to other SP results
mozi has integration with public-facing social applications on the roadmap. These integra-tions will support sending content uploaded into mozi to these services, so that the video content can be managed centrally (in mozi) and automatically updated.
mozi is an internet-hosted service located in secure data centres with worldwide reach. Together with a federated authentication service such as SAML, mozi can support authen-ticated access to content from inside the corporate network and from the internet. If the intention is to host content that would be visible to non-corporate users such as the gen-eral public, this can also be accommodated.
mozi supports using several types of enterprise CDN including Cisco CDS, BlueCoat etc. HTTP caching proxies and also peer-to-peer services such as Kontiki and Hive.
mozi is extensively tested on PCs, Macs, iOS devices and Android devices for both content upload and playback. The design of the mozi interface itself uses the latest web devel-opment techniques such as Responsive Web design to allow the interface to arrange the content in a way that best fits the device. mozi also works with apps that support the Me-dia RSS protocol to securely deliver content for offline playback, eg the Apple Podcasts app.
mozi supports comments and ratings
mozi is compatible with a wide variety of content creation tools. These range from the consumer type such as Windows Movie Maker and iMovie to more advanced tools such as Final Cut and Adobe Premiere. mozi can also receive, convert and store simple captures from iOS and Android mobile devices. mozi itself provides a webcam capture option
mozi converts any uploaded content into standards compliant H264/AAC MP4 files and streams, which are compatible with HLS playback. The quality of playback is customizable by the customer, but by default ranges from 200kbit/sec to 4000kbit/sec. mozi downcon-verts the uploaded video into lower quality variants but keeps the original available for fu-ture use. mozi uses the same content transformation standards that are used by Apple, Microsoft and Sony for their consumer-facing events.
mozi supports popular web, consumer and professional media formats. Examples include 3GP, AAC, AVI, FLV, MP4, WMV and MPEG-2. mozi supports the output from the complete range of professional and consumer video editing products
All incidents are assigned a severity rating from 1-4. Severity 1 (the highest) is defined by a multiple end-subcriber, customer impacting service interruption in which a production environment or service is 100% unavailable. Severity 2 is a multiple end-subcriber, cus-tomer impacting service interruption in which a production environment or service is par-tially (1-99%) unavailable. Severity 3 is defined by a single end-subscriber, single-instance customer impacting service interruption in which a production environment or service is partially or completely unavailable to the user. Severity 4 is defined as a support request or issue, that is not customer impacting. In each of these cases the event and assigned sever-ity is broadcast to the affected customer base using the email addressees nominated by the customer. As the target response time in each case is breached, the severity is updated and further notifications are sent to the customer. As engineers continue to work on the issue updates are sent to the affected customer base. Finally as a severe issue is resolved, a root cause analysis is developed and mitigation of this cause is defined and broadcast to the affected customer base.
Typically the customer‘s own support desk handles first line support. This might include help with authentication, volume controls, upload of content etc. Any issues that cannot be resolved by the efforts of the internal support desk can be escalated to the mozi support team. The mozi support team will work with the customer‘s support team to resolve the issue.
mozi runs on the Amazon Web Services platform, which delivers high performance global-ly. The core of the service that includes metadata and content storage can be held in a worldwide zone that meets the customer‘s legal requirements. For example, companies that require a hosting in a datacentre covered by EU Safe Harbour legislation can be host-ed in Ireland. mozi is able to deliver video content and other large assets worldwide via the comprehensively deployed CloudFront CDN, actual performance to the end user can vary depending on the user‘s network connection.
The webcasting platform is integrated with mozi, so that webcasts can be organized, searched and viewed through the mozi platform.
mozi delivers all services and content streams over HTTPS, or encrypted HLS. mozi ‘s HTTPS protection is rated A by Qualys SSL Labs. mozi integrates with SAML/ADFS to pro-vide strong authentication and access controls. mozi undergoes periodic penetration test-ing provided by third party companies
mozi has comprehensive analytics and reporting capabilities, linked down to the per-user level (when SAML is configured), mozi provides detailed stats on exactly how much video is being consumed and who is consuming it. As well as video playback reports mozi pro-vides very detailed analytics on user activity on the site generally, what types of devices they are using and where they are accessing the service from. These reports break down into a general statistics overview, audience and user specific stats, analysis of what con-tent is being accessed on the site, where the traffic is sourced from (eg, links from the in-tranet), and detailed playback information including the quality of the received stream over time.
mozi requires a modern web browser for the best experience. Supported web browsers include Internet Explorer 8+, Safari, Firefox and Chrome. or best video playback perfor-mance, including HLS support mozi recommends Flash Player 11
mozi can expose a dropbox on a simple private URL that external agencies can use to up-load content. Once uploaded the external agency can notify the content administrator, and they can download the content or make it available on the mozi site.