Are you William D. Roome?

Claim your profile

Publications (4)

  • Andre Beck · Robert E. Daugherty · J. Robert Ensor · [...] · William D. Roome
    [Show abstract] [Hide abstract] ABSTRACT: This paper discusses the design and implementation of blended services— composite services whose base component services interact within a common control structure. The paper focuses on blended services that combine aspects of Internet Protocol television (IPTV) and IP Multimedia Subsystem– (IMS)-based telephony services and, in particular, focuses on a service that blends TV viewing and telephone call-handling functions. If a subscriber to this service receives a telephone call while watching TV, the caller ID is displayed on the subscriber's TV screen and the subscriber can signal call control instructions using the set-top box remote control. In this service blend, functions from each base service are coordinated with actions in the other. The mechanism allowing this service is an information channel that allows status and control information to move between the subscriber's set-top box and the IMS system. The services described in this paper are built upon a software foundation called the Alcatel-Lucent Service Broker™ platform, a platform that has unique capabilities to support such an information channel and to serve as the gateway between IMS and digital TV. This foundation offers service developers a set of important functions for the creation of blended services. Specifically, the Alcatel-Lucent Service Broker offers a means of controlling the invocation of base services, a means of communicating through different protocols, and support for large-scale deployment and for service customization. © 2007 Alcatel-Lucent.
    Article · Mar 2007 · Bell Labs Technical Journal
  • Kristin F. Kocan · William D. Roome · Vinod Anupam
    [Show abstract] [Hide abstract] ABSTRACT: The 3rd Generation Partnership Project/3rd Generation Partnership Project 2 (3GPP/3GPP2) designates the service capability interaction manager (SCIM) as a functional component in the IP Multimedia Subsystem (IMS). This paper focuses on how the Lucent Service Broker™ product has been designed and how it would be deployed to perform as a SCIM in an IMS network. We discuss the challenges in managing service capability interaction and providing blended services that are encountered in IMS and show how Lucent Service Broker flexibility is needed to accommodate the breadth of challenges. We describe how the internal structure of the Lucent Service Broker and its application programming interface (API) offer this flexibility while minimizing the effort involved in adding new SCIM logic. We also demonstrate how the Lucent Service Broker may be used to marshal IMS application resources on behalf of revenue-generating applications in various usage scenarios. © 2006 Lucent Technologies Inc.
    Article · Dec 2006 · Bell Labs Technical Journal
  • Kristin F. Kocan · William D. Roome · Vinod Anupam
    [Show abstract] [Hide abstract] ABSTRACT: Service brokering considerably enhances advanced service architectures, such as IP Multimedia Subsystem (IMS), since the myriad applications potentially involved in a call or other session are located in the application layer and are separate and large grained. Through effective service brokering—that is, the effective blending and coordinating of services—interaction problems can be controlled and new composite services offering an enriched end-user experience can be provided. How can an effective service brokering capability be realized in a product when it must address needs not yet known? This question instigated the novel software approach (covered by filed Lucent patents) used in the Lucent Service Broker™ product. Adapting techniques used in Web servers and Session Initiation Protocol (SIP) servlet engines, but bringing to the design the special needs for service interaction and blending along with attendant needs for scalability and performance, the Lucent Service Broker was designed as a software engine with a powerful but easy-to-use API for customer programmability. This paper describes the software design of the Lucent Service Broker, particularly focusing on its novel aspects. © 2006 Lucent Technologies Inc.
    Article · Mar 2006 · Bell Labs Technical Journal
  • [Show abstract] [Hide abstract] ABSTRACT: This paper discusses the service broker, a function introduced into nextgeneration networks to manage interactions among applications, to reuse existing applications in a combined fashion, and/or to enable existing applications with capabilities such as presence, location, and policy. With the service broker, a minimal set of applications can be configured in a multiplicity of ways as its elements are brought into play in mix and match arrangements. For the degree of flexibility needed for the service broker to support unique service combinations, the service broker must be programmable. Various functional subcomponents enable these service broker capabilities. These subcomponents include service descriptors, the mechanisms to identify the logic that governs how the applications interact; user and endpoint data managers, the entities that present user-specific and endpoint-specific information; and session contexts, the transient entities that contain the context associated with an instance of call/session or multi-call/session. The session context includes state information and provides multi-session awareness that allows both simultaneous and sequential state-dependent sequential activity to be managed. This paper introduces a lightweight, programmable, Session Initiation Protocol (SIP)-centric service broker architecture and the concept of the “steplet,” which is central to this architecture. © 2005 Lucent Technologies Inc.
    Article · Mar 2005 · Bell Labs Technical Journal