Next generation of Copyright administration (NIM 4.0)


Release of new music in diversified markets…
To release a Copyright means that it’s available for licensing by Digital Service Providers (DSPs). As soon as the Copyright is registered, a note to DSPs will notify them of a change in administrative control and that a licence will have to be obtained from NIM services. This is as it works today, with the exception that in the future, the DSP does not have to negotiate individually licensing agreements. It can be obtained as a service from NIM.

It is not a requirement for our licencing and payment services. We still call the full-service Content as a Service (CaaS); the content can be hosted in the DSP own system or in any other CDN or NIM’s future services.

However, the ONLY way of licensing the content is via NIM’s ecosystem, and such anyone with access to NIM’s API can license any content they like if they have the CopyrightID (Guy Fletcher and Doug Flett’s Fallen Angel’s CopyrightID is:  ByAsaSDCeQ8R4hA7DBjZw3DCxG7ewQ7Excf7K4RZFzRZ) and some Royalties Tokens to pay for the license, i.e. CaaS is basically a pay as you go service…

Content as a Service (CaaS) (part of NIM 4.0).
Let me make one very important distinction. Whereas as NIM’s present activated service promotes a “software for managing, designing and publishing content”, The Content Cloud CaaS is used for managing/administration of content, never for its presentation.

The Content Cloud CaaS consists of a repository of channel-neutral (format-free) content. In other words, it is not tagged (hard-coded) for web delivery or mobile or any other channel. It is structured content that can be published to anything: web pages, mobile-device apps, wearable devices, store displays, the exploding Internet of Things, and any new channel that may appear in the future.

Customers can subscribe to content on areas of interest and have that content automatically delivered to them on the device and channel of their choosing.

At the same time is The Content Cloud CaaS designed for dynamic delivery of licensed or subscription-based content.

Each time the content is delivered, it changes to suit the context: the device being used, the location, the profile of the user, and other variables. NIM delivers “mobile-first” services.

Dynamic content delivery provides personalised content, giving customers what they want when they want it.

More specific and technical characteristics of The Content Cloud CaaS:

  1. The Content Cloud hosts the content repository in the cloud
  2. The content can be fetched via an API (Application Programmers Interface)
  3. The API returns the content in a well-structured format, such as JSON
  4. There is a mechanism for defining highly custom content structures
  5. There is a web interface for managing the content (the only similarity to WLCM)
  6. Webhooks helps the apps which depend on The Content Cloud to react to content updates
  7. The Content and presentation layers are separated, and the front-end doesn’t control how the content would look.

In short, The Content Cloud CaaS approach is simplification — it does less, but does it better — which brings more freedom on the consumer-facing end.

There is no silver bullet. However, The Content Cloud CaaS outperforms the traditional approach in the following cases:

  • Mobile apps content backend. Having content coming into a mobile app from a CaaS CMS is the best way to have dynamic in-app content without having to resubmit the app to the app marketplace. Also, using an existing solution as a backend is smarter than building your own (I speak from experience).
  • Multi-channel publishing. CaaS is also highly rewarding when content needs to be reused across different platforms: AND we do want to push the same content to a website and to mobile apps.
  • It is integrating with existing services and software stacks. The Content Cloud CaaS provides an API, is highly integration-friendly.
  • Highly custom UX. The traditional approach of the web age imposed strong design restrictions. Our CaaS job is to simply push content wherever and whenever necessary, and designers will be happy never to hear “not possible” from their fellow developers.
  • Programmatic (automatic) content creation. When content is already existing and coming from multiple sources, uploading content into one unified repository is ideally supported by creating Content via API as well (for instance – UGC User Generated Content).

The Network (CDN) – (part of NIM 4.0 future update)

The CDN is a network of servers that store content and deliver it to an audience spread across any area. The concept is to keep content on the CDN server closest to the end-user, wherever they are, to speed up the page load time and avoid global network bottlenecks.


The content Cloud CDN covers the entire world and uses CDN servers located in large cities in various countries to deliver content and applications to enterprise users and consumers.

CDN nodes and servers are deployed in multiple locations around the globe over multiple Internet backbones. These nodes cooperate with each other to satisfy data requests by end-users, transparently moving content to optimise the delivery process. The larger the size and scale of a CDN’s Edge Network deployments, the better the CDN.

CDNs generally push the Edge Network closer to end-users. The Edge Network grows outward from the origin server by the addition of co-location facilities, bandwidth, and servers. CDNs choose the best location for serving content while optimising for performance.

They may choose locations that are the fewest hops or the fewest number of network seconds away from the requesting client. CDNs choose the least expensive locations while optimising for cost. CDNs use various techniques such as web caching, server load balancing, and request routing to achieve the optimisation goals.

Because closer is better, web caches store popular content closer to the user. These shared network appliances reduce bandwidth requirements, reduce server load, and improve the client response times for content stored in the cache.

When building the network for NIM and the registration and financial service, we will be building a distributed file service as well (kind of added functionality for free).

The functionality of The Content Cloud CaaS is threefold.

  1. It’s a repository for all types of content, starting with music
  2. It’s a Content Delivery service
  3. It’s a Distributed files system that functions as a Digital rights management service

All based upon NIM technology

Share this article

Recent posts

Popular categories

Recent comments