article page | 1 | 2 | 3 |

connectivity, especially if we want to be able to allow the subscriber to move seamlessly from one network to the other during the same phone call.

In effect, we are creating an environment where a content-serving application can be connection-agnostic, utilizing the network resources of whatever type in a way that is appropriate to achieving the desired subscriber experience.

Obviously, a certain accommodation would have to be made for the subscriber terminal, and applications will need to be sophisticated enough to understand the terminal capabilities.

Once the service is activated, any changes to the parameters associated with one “arm” of the three part service, such as a decrease in the bandwidth contracted for by the subscriber, needs to be orchestrated with the application to reconfigure the overall service parameters.

Like this example, the more advanced and increasingly sophisticated applications will be required to traverse different types of connectivity that can reach the subscriber. The definition of what constitutes a service will evolve even further, and the need to establish traffic transport that is appropriate to the type of content will become even more necessary.

Without making that link between managing

This ultimately is the key to fielding the so-called “third screen” applications that take advantage of all the ways that a subscriber can interact with the application so a subscriber may watch a sporting event on the television, receive a secondary feed of information about players or statistics on the mobile phone, and view alternate camera angles of an instant replay on the PC. For this to be possible, the initial configuration of the service must incorporate an understanding of the capabilities of each of the receiving devices – PC, set-top box/TV, mobile phone – and must also establish the bandwidth requirements to deliver the content to each of the screens.

In fact, orchestration really must be extended across not only connectivity and content, but it also must encompass the end-user device’s parameters and characteristics in order to establish the appropriate requirements for the connectivity and content. If a device has certain graphics limitations, memory parameters, or a unique form factor, these characteristics must be part of the orchestration equation if the service is going to be managed on a true end-to-end basis.

connectivity and managing content, the subscriber experience cannot be guaranteed, and mismatches between content and the connectivity would be rampant. Just like in a world of only pickup trucks, a mismatch between the method of transportation and the intent of the transportation will surely result in a less than ideal experience for all.