USRE44412E1 - Digital home networks having a control point located on a wide area network - Google Patents

Digital home networks having a control point located on a wide area network Download PDF

Info

Publication number
USRE44412E1
USRE44412E1 US13/232,432 US201113232432A USRE44412E US RE44412 E1 USRE44412 E1 US RE44412E1 US 201113232432 A US201113232432 A US 201113232432A US RE44412 E USRE44412 E US RE44412E
Authority
US
United States
Prior art keywords
logic
network
media content
content delivery
cpp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US13/232,432
Inventor
Shamim A. Naqvi
Prasad S. Dorbala
Ellis L. Wong
Mahesh N. Ganmukhi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aylus Networks Inc
Original Assignee
Aylus Networks Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=46324021&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=USRE44412(E1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Priority claimed from US11/166,407 external-priority patent/US7792528B2/en
Priority claimed from US11/282,924 external-priority patent/US20060291487A1/en
Application filed by Aylus Networks Inc filed Critical Aylus Networks Inc
Priority to US13/232,432 priority Critical patent/USRE44412E1/en
Application granted granted Critical
Publication of USRE44412E1 publication Critical patent/USRE44412E1/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/12Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1225Details of core network interconnection arrangements
    • H04M7/123Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/146Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08Upper layer protocols
    • H04W80/10Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices

Definitions

  • the invention generally relates to IP Multimedia Subsystem (IMS) networks and, more specifically, to IMS users that use (perhaps multiple) discovered user endpoint devices.
  • IMS IP Multimedia Subsystem
  • ⁇ networks support both voice and data services.
  • mobile handsets are connected to a Base Transceiver Station (BTS) using a Radio Access Network (RAN) that uses a modulation scheme such as CDMA (Code Division Multiple Access) or GSM (Global System for Mobile communications).
  • RAN Radio Access Network
  • the BTSs are connected via fixed links to one or more Base Station Controllers (BSCs), and the BSCs are aggregated into switches called Mobile Switching Centers (MSCs).
  • BSC Base Station Controllers
  • MSC Mobile Switching Centers
  • the MSC is connected to the Public Land Mobile Network/Public Switched Telephone Network (PLMN/PSTN), typically through a gateway switch called the Gateway Mobile Switching Center (GMSC).
  • PLMN/PSTN Public Land Mobile Network/Public Switched Telephone Network
  • GMSC Gateway Mobile Switching Center
  • core network is used to collectively describe the MSC, GMSC and associated network elements.
  • Voice traffic uses the so called circuit-switched paradigm of communications in which circuits are assigned, i.e., dedicated, to a call for its entire duration; the voice traffic is carried using Time Division Multiplexing (TDM) switching technology.
  • Signaling traffic uses Signaling System 7 (SS7) typically as out of band circuits.
  • IP data service is offered to wireless clients by an overlay data network in which a packet control function (PCF) is introduced at the BSC level to connect BSCs to an IP-routed network.
  • PCF packet control function
  • the PCF is responsible for packetization of RAN traffic.
  • the PCF takes IP packets and reorganizes them for transmission as frames over the radio transport protocol.
  • the PCF packetizes radio protocol frames to IP packets. Data connections are handled by this overlay network and the MSC is used primarily to handle circuit-switched voice calls.
  • VoIP Voice over IP
  • MSC Voice over IP
  • MGW media gateway
  • the legacy switch is disaggregated into a control and multiplicity of media gateway (MGW) components.
  • the control component (sometimes called the soft switch) uses an open control protocol called the Media Gateway Control Protocol (MGCP) to manage the MGW.
  • MGCP Media Gateway Control Protocol
  • the MGW itself has the ability to accept both packet and circuit-switched traffic and convert one to the other, under the control of the soft switch. It is thus possible in 2.5G networks to carry both circuit-switched and packet-switched traffic.
  • a defining characteristic of 2.5G/3G multimedia services is that since the handset can send or receive IP data packets at any time, the IP context of the handset is maintained as long as the handset is powered on and connected to the network. This is in contrast to traditional telephony where the state of a connection is maintained only while a telephone call is in progress.
  • connection between the service logic and the application server is a “stateful” connection that needs to be maintained for the duration of the service being used.
  • stateful connections need to be maintained between the application server complex, hosted in the application domain, and the service logic complex hosted in the service logic domain, in a network servicing a large number of subscribers.
  • stateful connections that cross administrative domains have high networking costs and are difficult to maintain operationally.
  • IMS IP Multimedia Subsystem
  • FIG. 1 Typical of proposals for 3G network architecture is the IP Multimedia Subsystem (IMS) architecture, shown in FIG. 1 .
  • IMS is independent of the type of access network; that is, it applies both to wireless and landline networks. Examples of access networks include various flavors of Wi-Fi networks, GPRS, and HSDPA networks.
  • IMS uses Session Initiation Protocol (SIP) for control and signaling messages.
  • SIP Session Initiation Protocol
  • SIP is an IP-based signaling protocol designed for multimedia communications.
  • the IMS architecture introduces several control functions, i.e., functional entities, to manage the network.
  • the legacy circuit-switched traffic is handled by an Inter-working Function called the BGCF (Breakout gateway control function).
  • the MGW is controlled by a new function called the Media Gateway Control Function (MGCF), and the media processing functions are performed by the Media Resource Function Processor (MRFP), which is controlled by the Media Resource Control Function (MRCF).
  • the basic call server called the Call State Control Function (CSCF) is logically partitioned into three functional entities, the Proxy, Interrogating and Serving CSCF.
  • Proxy Call State Control Function is the first contact point for the handset, also referred to herein as the User Entity (UE,) within IMS and provides the following functions:
  • the Interrogating CSCF is mainly the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. It provides the following functions:
  • the Serving CSCF actually handles the session states in the network and provides the following functions:
  • the P-CSCF is the first point of contact for a UE (handset) in an IMS network.
  • the I-CSCF then helps in establishing which S-CSCF “owns” the UE.
  • FIG. 2 is a signaling diagram, showing the call flow for a UE when it first establishes contact with an IMS network.
  • the UE sends a “register” request to the proxy ( 201 , 202 ). Assuming the proxy determines that the UE is registering from a visiting domain, it queries the DNS to find the I-CSCF in the UE's home domain ( 203 ). The proxy then sends the registration information to the I-CSCF ( 204 ). The HSS checks if the user is already registered and sends the address of the S-CSCF in response ( 205 , 206 ). An authentication process now ensues in which the UE is challenged to provide valid authentication vectors ( 207 - 211 ). Once the authentication procedure is completed ( 212 - 218 ), the S-CSCF informs the HSS that the UE is registered ( 219 - 225 ).
  • the HSS provides initial filter codes (IFCs) to the S-CSCF.
  • the IFC maps the service codes with various application servers (ASs).
  • ASs application servers
  • the IFC is effectively the “call model” for the UE.
  • These call models are static objects downloaded during registration from the HSS. Every UE in the domain of the S-CSCF will, if they have the services enabled at all, have the same application servers (ASs) mapped to the same services. For example, push-to-talk service for each and every UE having such service will point to the same AS or point to an AS with identical service logic to provide the identical push-to-talk functionality.
  • Registered UEs may use services by initiating a new session establishment procedure depicted in FIG. 3 .
  • the Figure shows a session establishment request originating with a S-CSCF (called O-SCSCF) or I-CSCF (called O-ICSCF).
  • This request is routed to the “terminating” S-CSCF (T-SCSCF), which consults the callee's service profile ( 301 ).
  • the T-SCSCF sends an IMS service control request (ISC) to the corresponding application server (T-AS) that can handle this service request ( 302 ).
  • ISC IMS service control request
  • T-AS application server
  • the T-AS provides the service to the callee and terminates the session ( 303 ) and the S-CSCF terminates the application activation process ( 304 ).
  • This voice mail service is provided by an application server (AS) dedicated to this service and having service logic to provide such functionality.
  • AS application server
  • the S-CSCF transfers control to the voice mail application server when a certain service point trigger (SPT) occurs, i.e., an event occurs that causes a trigger within the SPT to “fire.”
  • SPT service point trigger
  • the IFCs that provide trigger points to the service logic of the S-CSCF are downloaded into the S-CSCF during user registration at session initiation time and remain fixed for the duration of the session.
  • the service profile described above that is consulted by the T-SCSCF is a static object in the sense that the information contained in it is defined once at the time of service inception.
  • the coverage area of a service provider is typically partitioned into geographical regions called cells.
  • Each cell is served by a BTS, i.e., the BTS radiates energy within a cell.
  • Allocating frequencies to cells in a judicious manner allows re-use of frequencies and, hence, to more efficient use of the operator's spectrum allocation.
  • a crucial component of wireless communication networks is the ability to hand off a moving handset from one BTS to a neighboring BTS.
  • Various handoff algorithms are known in the literature. Broadly speaking, all handoff technologies fall into one of two types: hard handoff, and soft handoff.
  • the connection between the current BTS and the handset is severed and a new connection is established between a new BTS and the handset while a telephone call is ongoing.
  • the decision to sever the old connection and start a new connection is based on a pre-determined threshold value of the received signal.
  • soft handoff technologies the signal strength from two (or more) BTS are compared and the one that has the higher value is selected.
  • the main advantage that handoffs provide is that ongoing calls remain connected as the handset roams in the coverage area. Since the region in which a BTS radiates is limited, a handset that roams out of the range of a BTS will lose connection with the BTS and hence any ongoing call will be dropped. Handoffs ensure that the handset remains connected to some BTS and any ongoing calls do not get dropped.
  • Wireless networks are now expected to provide broadcast content, video telephony, multimedia conferencing, video streaming services, file upload and download services, and interactive multimedia services.
  • the availability of network coverage supporting multimedia services is highly uneven. In some areas several networks may be available simultaneously that could be used by a handset, whereas in other regions there may be insufficient coverage to support a given network service. For example, at a given location one may have several short-range Wi-Fi or WiMax networks, or 1xRTT EVDO, that could provide multimedia services to a handset (assuming that the handset is capable of supporting multiple modulation schemes).
  • a handset however, has an inherent disadvantage since its form factor is generally not suitable for long term use as a display device.
  • the small size of the handset display screen is not amenable to long duration sessions or sessions in which the handset is jointly viewed by several users. In such cases it would be desirable to view the multimedia services on a larger LCD or a TV display device.
  • Many such devices support LAN connections directly or indirectly via commercially available media plugs.
  • such devices may also support short range wireless networks such as Wi-Fi and WiMax.
  • the wireless world is increasingly becoming a world of multiple networks. Some are short range and others support longer ranges of coverage. The information-carrying capacity of these networks varies widely from network to network. Handsets increasingly support multiple wireless connections, including both short range networks such as Bluetooth and Wi-Fi, and long range cellular networks.
  • the invention provides systems and methods for implementing digital home networks having a control point located on a wide area network.
  • the control point may be implemented on a serving node connected to the wide area network, and have the capability of working in conjunction with one or more control point proxies that are located in handsets connected to a 3G wireless network, or in remote control units located within the home.
  • the control point and control point proxies cooperatively negotiate media delivery from a user-selected media server, such as a home stereo or DVD player, to a user-selected media renderer, such as a TV display or the display on a handset.
  • the control point proxies also include VCR controls for controlling the presentation of the selected media delivery.
  • the invention features a method of controlling and delivering media content from a media server (MS) to a media renderer (MR) utilizing a wide area IMS network for control.
  • the method involves: provisioning a serving node in the IMS network with control point (CP) logic that includes logic to negotiate media content delivery with at least one of an MS and an MR; provisioning a user endpoint (UE) device of the IMS network with control point proxy (CPP) logic that includes (i) logic to negotiate media content delivery with at least one of an MS and an MR, (ii) logic to cooperate with CP logic to negotiate media content delivery between an MS and an MR, and (iii) VCR controls to control a presentation of content provided by the MS and rendered by the MR; in response to a media content delivery request, determining a network context of the UE and a network connectivity of the MS and MR; invoking the CPP logic and the CP logic to cooperatively negotiate media content delivery between an MS and an MR if one of the MS
  • the CPP logic is invoked to negotiate media content delivery between an MS and an MR if the MS and MR are both in communication with the UE via a local wireless network.
  • the local wireless network is a Wi-Fi network, a WiMax network, or a Bluetooth network.
  • the CP logic is invoked to negotiate media content delivery between an MS and an MR if neither the MS nor the MR are in communication the UE via the local wireless network.
  • the UE may be implemented on a handset, and the handset may include a display that is used as the media rendering device. At least one of the MS and the MR is on a 3G network and in communication with the serving node.
  • the UE is in communication with the MR or with both the MS and the MR via a local wireless network.
  • the CP logic negotiates service delivery from the MS, the MS being on a 3G network
  • the CPP logic in the UE negotiates delivery on the MR
  • the CP logic and CPP logic execute synchronization logic to complete the negotiation of delivery from the MS to the MR.
  • the UE communicates its network context to the serving node and the serving node informs the UE of the serving node's capabilities for negotiation with devices local to the UE.
  • the CP logic is configured to serve multiple unrelated devices running CPP logic; these devices can be handsets and remote control units.
  • the principal CPP can depend on the location of the user; for example, the user may use the CPP logic in the handset when the user is remote from the MR and use the CPP logic in a remote control unit when the user is local to the MR. If one of the MS and MR are remote from the UE, the CPP logic provides information about invoked VCR controls to the CP logic on the serving node to allow the CP logic to control the remote MS or MR.
  • the MS and the MR may both be a part of a digital home network.
  • the UE may discover local devices that can act as an MS or an MR by using Universal Plug and Play (UPnP) protocols.
  • UUPnP Universal Plug and Play
  • the MS and/or MR may announce their presence to the UE using at least one of UPnP protocols, Jini technology, RFID, and Bluetooth.
  • the CP/CPP may negotiate delivery of media content, it may negotiate of out-of-band media transfer between the MS and the MR.
  • FIG. 1 depicts a prior art IMS network.
  • FIGS. 2 and 3 are signal diagrams for a prior art IMS network.
  • FIG. 4 is a block diagram showing the principal elements of the described method.
  • FIG. 5 depicts logic for providing per user (or group) call models.
  • FIG. 6 depicts internal architecture of a certain embodiment of the invention.
  • FIG. 7 depicts logic for providing dynamic call models.
  • FIG. 8 is a simplified network diagram to illustrate the interaction between a UE, a CSCF and an application server.
  • FIG. 9 is a simplified network diagram to illustrate the interaction between a UE, a CSCF, a dynamic network topology database (or ME database) and policy database.
  • FIG. 10 depicts utilization of multiple access networks in a session having an AVS structure.
  • FIG. 11 depicts out-of-band mediation by a control point to use a potentially non-IMS service in an IMS context.
  • FIG. 12 depicts out-of-band mediation by a control point and a control point proxy to use a potentially non-IMS service in an IMS context.
  • FIG. 13 is a flowchart illustrating how devices and services are discovered and associated by the UE.
  • FIG. 14 is call flow diagram depicting the discovery of a device by a UE.
  • FIG. 15 is a call flow diagram depicting the discovery of a device by a UE and subsequent handoff to the device.
  • FIG. 16 is a call flow diagram depicting the discovery of a device by a UE and the establishment of a relay session to stream content to the device.
  • FIG. 17 is a call flow diagram depicting discovery of a device by a UE and subsequent streaming of trans-coded information to the device.
  • Preferred embodiments of the invention permit IMS user sessions to utilize devices that are discovered by the UE during the course of an IMS session.
  • the embodiments provide for the discovery of available devices, and for choosing whether to add a discovered device to the IMS session. The choice can be made to depend on physical and/or technical factors, such as whether the IMS session involves the use of content that could benefit from the incorporation of the associated device into the IMS session. For example, if the user is receiving video, and a large-screen TV set is discovered, it would be beneficial for the user to view the video on the large screen of the discovered TV set rather than on the small screen of a handset.
  • the decision to include the discovered device can be made to depend on a set of policies that involve business relationships (such as of the user to owner/operator of the available devices) and cost.
  • the described embodiments allow the signaling channel to remain intact (i.e., it is not generally handed over to an associated device) allowing for a consistent service experience (i.e., the application logic can remain in the domain of the original service provider).
  • FIG. 4 depicts relevant portions of an IMS network according to preferred embodiments of the invention.
  • the relevant portions include UE 402 , P-CSCF 404 , I-CSCF 406 , serving node 408 , HSS 422 , and call model database 416 .
  • the UE, P-CSCF 404 , I-CSCF 406 , and HSS are essentially conventional, though the content of HSS 422 is not, as described below.
  • the UE may have unconventional agent logic, namely PA logic 424 , and search module 426 , each of which is discussed in more detail below. All of these entities communicate using known and defined protocols.
  • Serving node 408 in preferred embodiments, includes S-CSCF logic 410 that is largely conventional though it includes certain modifications, discussed below. Serving node 408 also includes ME server logic 412 (more below) to store users' dynamic network topologies and other information, and provisioning logic 414 more below. (Alternatively, the ME server logic and the provisioning logic may each be a separate physical entity like an AS.) The ME server and provisioning logic essentially are co-located special purpose servers within node 408 . The serving node 408 , and particularly provisioning logic 414 , communicates with a call model database 416 . This database 416 (not the HSS as is the conventional case) is used to provide the call model information for a given user (more below).
  • This database 416 (not the HSS as is the conventional case) is used to provide the call model information for a given user (more below).
  • serving node 408 communicates with application servers (ASs) that include service logic for various services, e.g., voice mail, push-to-talk, etc.
  • ASs application servers
  • the UEs use predefined codes within service requests to identify the service of interest and/or these services can be triggered in known specified ways via SPTs (as is the conventional case).
  • FIG. 5 depicts the logic flow for provisioning a S-CSCF with distinct call models for each user.
  • the HSS provides initial filter codes (IFC) during UE registration (as is the conventional case).
  • IFC initial filter codes
  • SPTs service point triggers
  • the logic flow starts in 500 and proceeds to 502 in which the first service request is received after registration. Because of the default IFC, this service request will not trigger an AS corresponding to that service, and instead will trigger activation 504 of the provisioning logic 414 .
  • the provisioning logic 414 will then access 506 the call model database 416 .
  • One of the input parameters will identify the user.
  • the call model database 416 will retrieve a call model for that particular user. This call model will include the AS identifiers for the various services for that user.
  • the database 416 will provide 508 the call model information to the provisioning logic 414 which in turn will provide it to the S-CSCF logic 410 within serving node 408 .
  • the S-CSCF 410 will construct a new set of filter codes, i.e., NFC, and thus a new call model, for that user (and will trigger the service requested initially using the NFC).
  • the NFC will have SPTs identifying the corresponding ASs. This approach allows for dynamic construction of the NFCs (e.g., post registration) and allows the call model (e.g., NFC with associated SPTs) to be constructed uniquely for each user.
  • FIG. 6 depicts serving node 408 once multiple users have registered and been provisioned with their corresponding call models 602 a . . . n.
  • the different call models can point to different ASs for a given service, and they are not merely multiple instances of the same IFC/call model.
  • Multimedia network manager 606 receives service requests 608 from the IMS network and provides service responses 610 to the IMS network. It also routes received requests to the appropriate internal entities as shown.
  • ME server logic and Network Map policy manager 412 are responsible for receiving information (more below) indicating that the user's UE environment has changed with new capabilities or devices, and for building information structures and models to reflect these capabilities. In certain embodiments it also includes logic to implement specified policies on whether and how to utilize such capabilities.
  • Provisioned Service logic 414 is responsible for interacting with external or internal databases (e.g., database 416 of FIG. 4 ).
  • Media resource manager 612 is responsible for managing other resources (e.g., transcoders) that may be involved with a given service.
  • Multimedia service manager 604 is responsible for receiving requests from network manager 606 and for interacting with the other components to construct and build the per-user call model 602 . In simple cases this may involve creating call models with the help of the provisioning logic 414 and call model database 416 . In other cases the call model construction will be dynamic (more below) using new devices and capabilities (as well as associated policies), and in these instances the manager 604 will involve ME logic 412 , media resource manager 612 as well as handoff control application server 614 .
  • handoff denotes the transfer of a service delivery from one network and/or device to another network and/or device.
  • the handoff does not involve the dropping of an access network connection. This meaning contrasts with the meaning of the term that often appears in the prior art (referred to in the background section above), in which handoff means the dropping of a first connection in favor of a second connection based on the relative signal strengths of the two connections.
  • the context of an end user may change. For example, as a user roams, his or her context may change. Alternatively, even in non-roaming situations, the user context may change as new devices and capabilities emerge or become activated.
  • the user may be in close proximity to any number of devices that are capable of acting as a UE for a certain service (application). For example, the user may be near a TV that could be used to display multimedia content. Or the user may be in close proximity to a personal computer that could be used to receive multimedia information from a network connection, provided network connectivity and authorization to use such a device in this manner could be obtained.
  • the described methods allow a roaming user to discover (directly or indirectly) several kinds of information and invoke several kinds of corresponding relevant policies to consider when and how to use such capabilities and devices:
  • Policies may reside either in the UE or in a designated server in the network. In a preferred embodiment, the policies reside in the network.
  • a “dynamic profile” is constructed, in part, by logic that executes in the handset. This logic may be executed continuously, periodically at some network determined time interval, or on demand when the user requests a particular service. When executed, the logic senses (or otherwise discovers) the presence of associated devices in the immediate vicinity of the handset using a short-range wireless technology such as Wi-Fi.
  • UPnP Universal Plug and Play
  • dynamic device discovery and service discovery framework within a user's personal or home area network is performed.
  • UPnP may be used to create a dynamic profile of the immediate environment of the handset (i.e., user) service environment.
  • the dynamic device discovery mechanism is used to help create a personalized user area network map, which will serve as input to the switching/delivery logic.
  • Associated devices may announce their presence by a variety of means such as but not limited to Universal Plug and Play Devices (UPnP), Jini discoverable devices, RFID devices, and Bluetooth enabled devices.
  • UFP Universal Plug and Play Devices
  • Jini discoverable devices may announce their presence by a variety of means such as but not limited to Universal Plug and Play Devices (UPnP), Jini discoverable devices, RFID devices, and Bluetooth enabled devices.
  • the sensing logic in the handset receives such broadcast information and assembles it to construct a dynamic profile of the user's immediate context. Since this context changes as the user roams, the dynamic profile changes to reflect the current vicinity of the handset.
  • the dynamic profile is communicated to the serving node 408 .
  • this information may be communicated as parameters (e.g., by overloading information elements [IEs] of Session Description Protocol (SDP) messages) in conjunction with a special service request dedicated to communicating potential UE devices.
  • IEs information elements
  • SDP Session Description Protocol
  • a personal agent (PA) having PA logic 424 executes in UE (handset) 402 and includes the sensing logic to discover such other potential UEs or associated devices (more below).
  • the dynamic profile of the user's immediate environment is communicated to the ME logic 412 . This is done by having the ME server invoked in response to the special service request from the UE for communicating such discovered devices and capabilities.
  • the ME service will construct topologies and maps to identify the potential UEs, other networks, etc., to reflect the new devices and capabilities discovered or sensed in the UE's vicinity that could potentially be used by a given user.
  • the handset's User Agent profile (UAProf) or Composite Capabilities/Preference Profiles (CC/PP) representing device capabilities and user preferences is used to personalize the multimedia service delivery framework.
  • Serving node 408 will gather the UAProf or CC/PP from the endpoint devices to guide control of not only the rendering and trans-coding of content to be delivered to that device, but also the generation of the call agent as well as the decision to execute that service agent within the network or at the endpoint.
  • the personal agent supports an automated network and service discovery mechanism, such as the industry standard Universal Plug and Play (UpnP) framework, to establish association with and control of those networked devices.
  • the networked devices that the PA can be associated with through the discovery procedure can be connected to the mobile handset via wireless connectivity, such as Bluetooth, Jini, self-identifying label technologies such as RFID, or Wi-Fi, or via wired connectivity, such as USB or IEEE 1394 links.
  • the static user profile downloaded by the HSS into the S-CSCF at registration time is provisioned by the network operator to contain the address of the ME server.
  • every communication of the dynamic profile originating from the UE and received by the S-CSCF causes a SPT trigger to fire, and control is transferred to the corresponding ME server.
  • the serving node 408 and more particularly the ME server 412 becomes aware of the immediate context of the UE (handset).
  • the ME server consults a database of policies described by the service operator. These policy descriptions may be co-located with the ME logic and even the S-CSCF logic (see, e.g., FIG. 6 ). These policies prescribe certain actions that depend on the data contained in the dynamic profile. For example, a policy can require that if the UE sensing logic discovers a Wi-Fi connection in its immediate vicinity, then this discovered network should be used for originating session requests. Specific logic associated with this policy is then executed to send directions to the PA to enforce this directive at the UE level.
  • MVNO Mobile Virtual Network Operator
  • a MVNO is an operator that use the radio spectrum license-holder's underlying network facilities to offer services to the consumer. MVNOs do not typically own network infrastructure or spectrum license).
  • Another MVNO may, in general, have a completely different set of policies. Policies may not only be specified by the MVNO but also by end users, provided the network interfaces allow the users to specify actions that should be taken when certain events and situations are discovered in the UE's environment. Such user specified policies may over-ride policies specified by the MVNO.
  • FIG. 7 is a flow diagram illustrating the customization of service logic.
  • the logic starts in step 700 and proceeds to step 702 in which the PA logic 424 on the UE discovers or senses its immediate environment or context and constructs a message specifying this dynamic context. This message may include information about, new devices that could be used to receive multimedia information, new network connections that terminate and emanate from such devices, and new device capabilities.
  • the PA on the UE sends the message to S-CSCF ( 704 ) and the message either causes an SPT trigger or it does not, depending on how the IFC or NFC is constructed ( 706 ). If the message is triggering event, the logic proceeds to step 708 in which control is transferred to the ME server; otherwise the logic terminates ( 799 ).
  • the ME server updates its internal database to reflect the information communicated in the message from the PA in the UE ( 710 ).
  • the ME server then applies any relevant policies that will determine, for example, whether and how to utilize newly discovered devices and capabilities ( 712 ), and the logic determines whether any action is specified by the policy ( 714 ). If so, the specified action is initiated ( 716 ). This can be done by customizing the PA logic 424 on the UE or by customizing the AS logic. For example, in a typical embodiment, S-CSCF logic 410 will be modified to initiate or trigger the specified actions after the ME logic has updated its models accordingly and perhaps after a new dynamic call model is instructed for that particular user to reflect new devices and capabilities.
  • S-CSCF logic 410 is not hosted within a serving node 408 as shown in FIG. 4 ; that is, the S-CSCF 410 is not constrained to be hosted by the MVNO domain.
  • the S-CSCF remains hosted in the IMS serving domain of the network operator and is a separate entity, as in a conventional IMS network, and the ME server and provisioning logic are configured as ASs, though, as explained above, they do not provide conventional IMS services and instead are used in the construction of dynamic call models.
  • FIG. 8 The interactions between the CSCF and an AS are summarized in FIG. 8 .
  • ASs application servers
  • FIG. 8 the network is simplified (for descriptive purposes) to show only one AS 802 , but in practice there will be multiple ASs.
  • Service requests are sent (directly or indirectly) from a UE 402 (see also FIG. 4 ) to a S-CSCF 410 (see also FIG. 4 ).
  • the S-CSCF uses its internal call model (see, e.g., 602 of FIG. 6 ) to invoke a corresponding application server.
  • the call-model 602 (i.e., state machine) executing in the S-CSCF 410 for this UE is modified to take into consideration the newly discovered devices and network connections as described herein.
  • This newly discovered information is stored in the ME server 412 .
  • the discovery is done by sensing logic resident in the UE and may be communicated to the ME server periodically, or when discovered, or at pre-designated intervals. As discussed above, this communication may be done, for example, by overloading the information elements of the SDP.
  • the interaction between the ME server 412 and the CSCF 410 is shown in FIG. 9 .
  • the CSCF 410 is invoked with messages (or overloaded messages) that include information about discovered devices, network connections, new capabilities, etc.
  • the CSCF 410 then invokes the ME server 412 which in turn consults the policy database 902 .
  • a subscriber wanting to view multimedia content from an Internet server on his handset initiates an IMS request to serving node 408 .
  • the request emanates from the UE to the P-CSCF and onwards to the S-CSCF as explained above in connection with FIG. 1 .
  • From the S-CSCF it is routed to the ME (acting as an Application server) so as to perform per subscriber customization, as explained in connection with FIG. 4 .
  • This request then causes a connection to be made to the serving node 408 (explained in more detail later) and an IMS session is established between serving node 408 and the UE using the access network to which the P-CSCF is attached.
  • This IMS session is uniquely identified by an IMS Charging ID (ICID) assigned by the P-CSCF.
  • IMS Charging ID IMS Charging ID
  • PPP (Point to Point Protocol) session 1002 has its own unique identifier called the Transport Charging ID (TCID) 1006 assigned by the device (Packet data Gateway or Packet Control Function in the BSC) from which the PPP session emanates.
  • TCID 1006 and ICID 1008 together uniquely identify the multimedia session in which the SIP/IMS signaling is embedded within the IP/PPP connection.
  • the ME function 412 creates or modifies a computational entity called an AVS (Audio Video Session) 1004 to model and control (in part) the actual access network connections for a given user.
  • the call model 602 a discussed previously, is constructed first, based on the resources and policies.
  • the AVS represents what is actually going on, or intended to take place, or actually takes place (i.e., dynamically modifying to context). That is, the AVS represents the actual connections registered or to be registered in response to a given service request. If each access network connection is considered to be a “session”, then the AVS is a form of meta-session, or a super-session incorporating the access network sessions.
  • Each AVS is uniquely identified by a AVID (Audio Video session ID) that is a function of the underlying TCID and the ICID.
  • An AVS is a representation of every access network that the UE encounters while roaming. For each new access network this representation creates a new “leg” (called Incoming Call Leg-ICL 1012 , 1014 ). Each ICL has associated with it a TCID and an ICID (generated by other network elements) that together uniquely identify the session corresponding to that access network. Since the AVS 1004 has access to registration information of the UE, it knows that various ICLs (and hence various TCID+ICID combinations) really belong to the same UE, and hence, for each UE, the AVS representation captures all the access networks that the handset encounters. And since some access networks may support circuit-switched (CS) transport mode whereas others may support packet-switched (PS) transport modes, ICLs may be CS or PS supporting ICLs.
  • CS circuit-switched
  • PS packet-switched
  • Network policies will generally govern the co-existence of ICLs within a single AVS.
  • current telecomm networks do not support the idea of a UE being associated with more than one circuit-switched network. This translates into an AVS constraint: “only one ICL may exist for CS sessions.”
  • Another example of a constraint is provided by current so-called Class B handsets in which both a CS and PS protocol stack are available but only one such stack can execute at any time.
  • Class B+Wi-Fi handsets in which a CS session and a Wi-Fi session, or a Wi-Fi and a PS session can coexist.
  • policies can be contained in the policy database, and as with the construction of call models, the policies may be accessed when modifying AVSs.
  • a class B UE is engaged in a PS session watching Mobile TV.
  • the UE roams into a Wi-Fi zone and a handoff happens, after which the MobileTV feed uses the Wi-Fi network.
  • the previous PS session is idle and could be cleared.
  • keeping it around serves a useful purpose. For example, suppose a voice call arrives for this UE. Since the CS stack is not executing in the UE, the call will normally be routed to voice mail without the user being informed of the call. But suppose a serving node 408 is informed of the arrival of this call (as explained below), and then uses the PS session to present a dialog box giving the user a choice to take the voice call.
  • This example shows the usefulness of having more than one session (more than one ICL) active. Policies governing a given service will dictate whether or not to keep a leg active. Moreover, sometimes a leg may be unavoidably dropped, for example via lack of sufficient use, or because of signal issues.
  • the serving node 408 includes one AVS per user.
  • an AVS 1004 can include multiple ICLs 1012 , 1014 and an OCL or OGL 1010 (outgoing call leg).
  • the AVS also includes a control point 1016 .
  • the control point (CP) may be used to provide mediation between some form of service or server and the UE.
  • each leg may have effectuation routines to perform or effectuate routine functions on a given access network, such as responding to “are you alive” messages.
  • the serving node 408 manipulates the AVS it corresponds to actions in the “real world.” For example, adding an ICL means getting registered on that access network.
  • FIG. 11 illustrates how certain components, particularly the CP 1016 interact with other entities. It also shows how to incorporate non-IMS (legacy) services into a network, or to “marry” multiple networks.
  • the CP 1016 within AVS 1004 can perform out of band mediation so that a media server (MS) 1104 somewhere in the network can deliver content to a media renderer (MR) program 1106 on the UE, which receives and presents such content.
  • MS media server
  • MR media renderer
  • CP 1016 is connected to the MS 1102 , which in turn establishes a connection to the serving node 408 (using network server specific protocols).
  • the connection between the CP and the MS is internal to the ME 412 .
  • the connection between the MS and the serving node 408 is an Outgoing Leg 1010 of the AVS. That is, AVS 1004 models this connection as outgoing leg component 1010 .
  • CP 1016 is also connected to MR 1104 , which preferable may reside in the UE.
  • the connection between the CP and the MR is an Incoming Leg, e.g., 1012 . That is, AVS 1004 models this connection as incoming leg component 1012 or 1014 .
  • the CP negotiates multimedia content delivery with the MS and instructs the MS to deliver content to an address corresponding to the MR on the UE.
  • the instructions provided during such mediation will conform to the environment, context, and capabilities of the UE.
  • CP 1016 also negotiates media rendering with the MR itself in each Incoming Leg of the AVS. That is, the CP effectively instructs the MR to start expecting content from the MS, and to present such. Again, the instructions provided during such mediation will conform to the environment, context, and capabilities of the UE.
  • the newly discovered access network connection is modeled and included into the current AVS as an Incoming Leg.
  • Each access network available to a UE corresponds to an Incoming Leg of an AVS and the connection between the CP and MS corresponds to the Outgoing Leg of the AVS.
  • the UE has sensed three different access networks and policy allows all three, then there are three distinct access network connections between the UE and the S-CSCF. In such a situation, there are signaling and bearer channels in each access network that can be utilized. It is a matter of policy that decides which signaling channel within an access network is to be used and which channels within an access network is to be used for bearer traffic. In the case when coverage of an access network is lost (for example, due to roaming of the UE), the corresponding access network connection and the associated AVS Incoming Leg is “cleared” under S-CSCF serving logic control by the P-CSCF.
  • the proposed IMS specifications allow the UE to connect to an access network.
  • Preferred embodiments of the present invention allow the UE to remain in simultaneous connection (or potential use) with multiple access networks and the choice of which access network to deliver a particular service to the UE is to be made by policies resident in the ME function in the serving node of the network. That is, the AVS facilitates control of multiple access networks (both signaling and bearer) and allows choices to be made (by the system and perhaps the user) as to which network to use in a given context and time.
  • a Class A handset can have multiple packet sessions and a circuit-switched session simultaneously active in the handset.
  • the corresponding AVS may have multiple Incoming Legs corresponding to one circuit-switched and multiple packet-switched sessions.
  • Another type of handset, called a Class B, handset only supports either a circuit-switched session or a packet session at any given time. If the handset roams into a Wi-Fi area from a cellular area, the circuit-switched session is replaced by a new packet-switched session supported by the new Wi-Fi network in a Class B handset; in a Class A handset the circuit-switched session can be allowed to persist.
  • Scenarios 1-4 show that by having access to multiple access networks under mobility situations, the described embodiments allow services that use a combination of packet and circuit-switched access network technologies.
  • control point (CP) 1016 is the mechanism used to allow “out of band” media transport under control of IMS.
  • every AVS 1004 has an associated CP 1016 , for example, logically within the AVS. More specifically, each AVS is designated to have an “Outgoing Leg” (OCL) 1010 that contains a CP.
  • OCL Outgoing Leg
  • the CP has capability to transact with an Application Server (AS) using a standard protocol, such as RTSP, and it has the capability to transact with programs in the UE called Media Renders (MRs), again using standard protocols such as SIP, or SOAP/HTTP.
  • AS Application Server
  • MRs Media Renders
  • the CP itself may be considered an Application Server (AS) by the S-CSCF (i.e., interacted with as if it were an AS).
  • a UE requesting Mobile TV service This request emanates from the UE (on an ICL) and is forwarded by the S-CSCF to the CP 1016 acting as an AS (in standard IMS fashion). Since the CP acting as an AS has access to IMS charging and authentication mechanisms, the first objective of re-using IMS infrastructure for legacy services is fulfilled.
  • the CP contacts the MobileTV server (e.g., illustrated as Content Server 1018 in FIG. 10 ) using RTSP protocol.
  • the CP could pass control to another Application Server that now contacts the MobileTV server using RTSP′′, i.e., there is a chain of Application Servers as in standard IMS.
  • the CP instructs the MobileTV server to initiate sending media to the UE (at a designed IP address) and instructs the MR in the UE to render the incoming media.
  • This media transfer from the MS to the MR may use an out-of-band (non IMS) transport such as RTP/UDP/IP.
  • IMS out-of-band
  • the MobileTV server may not support the capability of receiving a service request from client A and initiating service to a client at a different address. In this case the MobileTV server will be asked to send the media to the CP's address and it will be forwarded to the UE by the CP, a process called re-NATting).
  • the communication between the CP and the UE for setting up media rendering and for other functions uses valuable spectrum.
  • the relationship between an MR and a media server can be fixed a priori and pre-provisioned.
  • the CP always picks a pre-designated MR for a particular media server.
  • wireless spectrum-consuming communications between the CP, media servers and media renderers are reduced by introducing a CP Proxy (CPP) that resides in the UE.
  • CCP CP Proxy
  • UPnP architecture includes three functional entities: control point (CP), media server (MS), and media renderer (MR). These may be implemented in different physical devices.
  • control point CP
  • MS media server
  • MR media renderer
  • the MS and MR typically reside in a TV set and the CP in a remote control unit.
  • MS and MR entities represent abstractions that capture the essence of media servers and media renderers.
  • the abstractions allow programmers to write general-purpose software that deals with the properties of these entities without having to deal with their inner workings. The handling of these inner workings is left to the implementation of the media server and the media renderer themselves.
  • a program desires to issue a “suspend” command to an MS, it may use the MS's defined interface to issue that command. It is left to the MS to implement the “suspend” command.
  • Communications between the CP and an MS and MR use the SOAP/HTTP protocols.
  • Direct communication between an MS and an MR is referred to as “out of band,” since is up to the MS and MR to select the protocol.
  • One such protocol is RTSP/RTP.
  • the MS implements a video player
  • the MR implements an LCD display
  • the CP implements a remote control unit.
  • the CP queries the MS for a contents directory and presents that on the display unit, allowing content to be selected for rendering.
  • the commands between the CP and MS, and between the CP and MR use SOAP/HTTP.
  • the communication between MS and MR could use RTSP/RTP.
  • the wireless network could be used to carry a control protocol between the these three entities, akin to SOAP/HTTP (but perhaps a more secure version).
  • SOAP/HTTP but perhaps a more secure version
  • the UPnP architecture is extended into a wide area network environment.
  • One approach, illustrated in FIG. 12 reduces control message traffic over the wireless network by moving CP 1016 into a network element and running one or more CPPs 1202 in one or more handset(s).
  • This architecture has two advantages. First, the communication between CP 1016 and MS 1102 need no longer use the wireless network. Second, when CPP 1202 is in close proximity to MR 1104 , the handset (CPP) can use an available Personal Area Network (PAN), such as Wi-Fi, to communicate with the MR. Since the wide area wireless network uses expensive spectrum, these advantages can afford considerable cost savings.
  • PAN Personal Area Network
  • the CP and the CPPs need a synchronization protocol. Communication between the CP and the CPP could be optimized by using off-peak times to communicate and by making the CPP as independent of the CP as possible.
  • Moving the control point into the wide area network enables a user to connect to services provided by MSs that are not located in the home, such as foreign television stations.
  • MSs whether in the home or not, can now be rendered on MRs outside the home, such as on the handset itself, or on an MR that is in proximity to the handset running the CPP when the handset is outside the home, as described above.
  • CP 1016 running in the SN can support multiple CPPs.
  • the remote control unit When the user is inside the home, he may prefer to use the remote control unit as the CPP since it may have a better form factor for VCR-type controls.
  • the user when the user is outside the home, he invokes the CPP on the handset in order to maintain connection and control with the home network.
  • a subscriber requests a media service to be rendered on a home Wi-Fi-enabled display device.
  • CPP 1202 communicates with CP 1016 via internal interface 1204 using the wide area wireless network. Subsequent communication between CP 1016 and MS 1102 , or between CPP 1202 and MR 1104 need not use the wireless network.
  • CPP 1202 Upon receiving confirmation from CP 1016 , CPP 1202 instructs MR 1104 to negotiate an out-of-band service request with MS 1102 .
  • the CPP in the UE negotiates the association between the MS and MR. In this case there is no need to involve the CP in the SN, since this would involve unnecessary use of wireless bandwidth. Conversely, when the UE is not in the proximity of either the desired MS or the desired MR, the CP handles the negotiation and association of both the MR and MS, using fixed communication links instead of wireless links.
  • moving the CP into a network element, such as the serving node of an IMS session, and placing the CPP into the handset optimizes usage of the wireless spectrum usage.
  • normal telephony includes supplementary features such as call diversion, three-way calling, and voicemail.
  • the CP does not migrate to the core network, but continues to reside in the handset.
  • this peer-to-peer style architecture there is no core network element, but the peer-to-peer signaling uses the valuable and limited resources of the wireless spectrum.
  • the network-based architecture consumes less wireless spectrum.
  • CPP 1202 has local service logic that decides what MR to pick for a particular media server.
  • the CP-MR negotiation is transformed into CPP-MR negotiation (which is local to a UE and hence does not use spectrum).
  • the CPP policies and logic can be updated periodically from the network-resident CP at opportune times.
  • MVNO-customized logic may be applied to so-called hybrid networks.
  • a hybrid network is a combination of two or more individual networks. Examples of digital broadcast networks for joint use are DVB-H (Digital Video Broadcast—Handheld), and Media FLO (Forward Link Only).
  • the broadcast network provides a high capacity but one-way transport for multimedia (video) traffic, while the UMTS (Universal Mobile Telecommunications System) network (or other network) may provide lower capacity two-way transport for interactive services.
  • the UMTS network is used for control and signaling purposes for the services offered by the broadcast component network.
  • the UMTS network supplements the digital broadcast network by providing a control network or a network for user interactivity functions.
  • the broadcast network may supplement a UMTS (or other) network by providing certain broadcast functionality.
  • the handset Since the PA runs in mobile handset environment, the handset has a direct logical service interface to the Internet Wide Area Network (WAN) via the 2G/3G wireless network. From the UPnP device architecture perspective, the PA serves as an Internet Gateway Device (IGD).
  • IGD is an “edge” interconnect device between a residential Local Area Network (LAN) and the Wide Area Network (WAN), providing connectivity to the Internet.
  • the IGD typically runs in the local network environment, e.g., on a PC in the WLAN environment.
  • the discovery, registration, and use of an associated device corresponds to the setting up of a new incoming leg of the AVS session.
  • the ME server determines whether there is an advantage to be gained from switching the media rendering from the renderer in the handset to a renderer in a discovered device.
  • the CPP can then offer a choice to the user as to whether to switch to the new renderer, or the switch can be performed automatically.
  • a UPnP service manager is provided in the PA to organize the services discovered, as shown in FIG. 13 .
  • the UPnP service manager performs device/service search and also listens to advertisements being sent out by new devices.
  • FIG. 13 illustrates exemplary logic for the service manager.
  • the service manager logic starts ( 1302 ) when the PA detects the presence of a PAN.
  • the service manager consults a directory of services that are potentially available on the PAN ( 1304 ). If the UE is seeking to use a service, and it finds the service present in the directory, the service manager joins the PAN ( 1306 ) and broadcasts a search message ( 1308 ).
  • the PA When the PA receives responses from the services on the PAN, it determines whether the user is authorized to use the desired service, and whether the service is still available ( 1310 ). If the answer is yes, the process for associating the PA with the new service takes place ( 1312 , 1314 , 1316 , 1318 , and 1320 ). If the UE is seeking to provide a service in the PAN, and the service is not already present in the PAN ( 1304 ), the service manager joins the network ( 1322 ) and broadcasts an advertising message ( 1324 ). In response, it may receive messages from the devices on the PAN ( 1326 ), and then proceed to associate itself with PAN ( 1314 , 1316 , 1318 , and 1320 ).
  • search module 426 (see FIG. 4 ) running in PA logic 424
  • advertisement module running in a device to be added to the network.
  • Search module 426 is a UDP-based function in the PA that broadcasts search messages whenever the user wants to search for new devices. It communicates with the user interface of the service manager and updates a list (in the PA logic 424 ) of discovered devices on the service manager when it finds a new device. It determines whether or not the device is new by matching its Universally Unique Identifier (UUID) against those of the devices already discovered. Each device has a unique UUID.
  • UUID Universally Unique Identifier
  • Search Module 426 consists of the following procedures:
  • the discovery protocol allows control point proxies, such as the PA, to search for devices of interest in the network.
  • a search is carried out by multicasting a search message with a pattern equal to a type or identifier for a device or service.
  • Responses from service providers/devices contain discovery messages that are essentially identical to those advertised by newly connected devices.
  • the responses to the outgoing discovery messages from the PA are similar to the messages the service providers/devices are themselves unicasting as their own advertising messages, as described below.
  • the former are unicast while the latter are multicast.
  • Below is a format of a Search message:
  • the discovered device sends a message to the M-SEARCH source IP address and port that sent the discovery request to the multicast channel.
  • This response follows the same pattern as listed for NOTIFY with “ssdp: alive” (see below in the description of the advertising module) except that a search target (ST) header is used instead of the new target (NT) header.
  • ST search target
  • NT new target
  • the PA After the PA has discovered a device, the PA still knows very little about the device. In order to learn more about the device and its capabilities, or to interact with the device, the PA retrieves the device's description from the URL provided by the device in the discovery message. The PA sends the following request header to the discovered device:
  • HOST host for description: port for description
  • the ‘Host’ and ‘Accept’ header fields in the request headers are sent, following normal conventions, such as from HTML.
  • the socket is created, where the HostName and RemotePort properties are set to the values specified in the URL, the request header block is then sent to the discovered device, which consists of the command (GET) and the other header fields defined above.
  • GET command
  • a sample of a device description in the XML format is shown:
  • a device When a device is added to the network, it advertises its services to control points by multicasting discovery messages to a standard address and port at regular time intervals. Serving as an UPnP control point, the PA listens to this port to detect when new capabilities are available on the network.
  • Each advertisement message contains information specific to the embedded device or service as well as information about its enclosing device. Messages should include the duration until the advertisements expire. If the device becomes unavailable, the device will either explicitly cancel its advertisements, or wait for the advertisements to expire on their own.
  • the advertisement module in the PA listens for advertisement messages. It is also a UDP-based application that listens on port 1900 (as given in the UPnP specifications). It communicates with the user interface of the service manager and updates the list of discovered devices on the service manager when it finds a new device. It determines whether or not the device is new by matching its UUID against those of the devices already discovered.
  • the service manager is needed because more than one service may be present in the Personal Area Network (PAN) and the manager provides an easy and intuitive way for the user to manage all the discovered services/devices.
  • the service manager is responsible for communicating the updated PAN neighborhood configuration (i.e., context) of the mobile handset to serving node 408 .
  • the discovered device and service will be reported to the serving node 408 in a SIP message which includes an SDP extension header.
  • the service manager enables the mobile handset user to accomplish this.
  • a timer is started whose value depends on the cache-expiry value sent by the device. Once this timer expires, the device/service is removed from the list. However, if an advertisement message is received from that device the timer is restarted.
  • the format of the multicast message is as follows: values in italics are placeholders for actual values.
  • NTS ssdp: alive
  • the following case illustrates by way of example a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms.
  • the new device to be associated with the PA client is powered on and starts advertising its service and device descriptions.
  • the new device might be a PC with IGD software, whose display will be used as a media renderer.
  • the device when a device is added to the network, the device is allowed to advertise its presence on the network using Simple Service Discovery Protocol (SSDP).
  • SSDP Simple Service Discovery Protocol
  • the UPnP discovery procedure operates transparently on top of various wireless or wired PANs or Home Area Networks (HANs), such as Bluetooth, Wi-Fi, USB, etc.
  • HANs Home Area Networks
  • the control point When a control point such as the PA IMS/SIP mobile client is added, the control point is similarly allowed to generate a multicast search for devices.
  • the message exchange consists of a brief description of the device that includes the UPnP device type, the device ID, and a URL to the full device description.
  • the message formats are as described above.
  • the UE obtains more information about a specific device by retrieving the full description from the URL with HTTP GET.
  • the full description is composed of a device description and a service description.
  • the device and service descriptions are XML documents and are constructed by the device vendor with the aid of the device and service template schemas.
  • the service description contains details of the hosted API commands, which are called actions, along with parameters, which are called arguments.
  • the PA IMS/SIP mobile client has established an association with that device, completing the UPnP device discovery process.
  • the following case illustrates a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms, and the serving node triggering a handoff procedure from the PA client to the associated device to initiate a real time streaming protocol (RTSP) streaming session.
  • RTSP real time streaming protocol
  • an IMS/SIP session has been established between the PA and the Media Server Control AS in the serving node.
  • the PA IMS/SIP mobile client located in the user's home network, includes the newly associated device information in the SIP RE-INVITE message it sends to Handoff Control Application Server (AS) module 614 (within serving node 408 ).
  • AS Handoff Control Application Server
  • the mobile station (MS) or UE includes its original SIP user identifier into the from-field of the SIP header.
  • the information about the newly discovered device is added to the ME framework database entry associated with the mobile device.
  • the new device discovery/association event may trigger a handoff control decision to be executed in the Handoff Control Application Server module 614 .
  • This decision is driven by policy logic in policy database 902 (see FIG. 9 ).
  • the policy logic includes rules that depend on technical specifications of the discovered device that determine whether the discovered device, if associated with the ongoing IMS session, would add value to the user.
  • the policy logic may also include business-based rules that reflect the relationship of the user to the owner/operator of a discovered device.
  • the response from the serving node towards the PA mobile client includes the handoff control information.
  • the PA IMS/SIP mobile client issues a SOAP remote procedure call to the media renderer (i.e., the device that renders the media) to initiate a RTSP streaming session.
  • Services i.e., media renderer
  • state tables updated so that control points can obtain meaningful values.
  • the media renderer initiates the RTSP signaling transactions to establish a streaming session with the media server.
  • the PA mobile client sends a SOAP remote procedure call to the media renderer to PLAY the multimedia stream.
  • the media renderer sends the RTSP Play command to the streaming media server to start the media stream.
  • This stream is out-of-band transport of the media stream from the media server to the media renderer.
  • the user may optionally decide to disengage the serving node from controlling the media server and allow the media control to be handled directly from the media renderer.
  • the PA mobile client sends a SIP RE-INVITE message towards the media server control application in the serving node to disengage.
  • the following case illustrates a session that involves the PA client discovering an associated device via UPnP discovery mechanisms, and the serving node triggering a relay procedure to allow RTSP streaming content to be relayed from the PA client to the associated device.
  • the media transport takes place over the 2G/3G network to the handset, and from the handset it is relayed to a discovered associated device using a WLAN/PAN.
  • the PA acts as a SIP UE and an IMS/SIP session has been established between the PA and the Media Server Control AS in the serving node.
  • the new device discovery/association event triggers an action to have the PA relay the content to the newly associated device.
  • the response from the serving node towards the PA client includes the relay control information.
  • the PA client issues a SOAP remote procedure call to the associated device, which, in this case, is a media renderer, to establish a UPnP LAN connection.
  • the associated device which, in this case, is a media renderer, to establish a UPnP LAN connection.
  • the PA client serving as an UPnP media server device initiates the RTSP signaling transactions to establish a streaming session.
  • the associated device operating as an UPnP media renderer sends a SOAP remote procedure call to the PA client to initiate the PLAY action to start the multimedia stream.
  • the PA client sends the RTSP PLAY command to the multimedia server to start the media stream.
  • the user may optionally decide to disengage the serving node from controlling the media server and allow the media control to be handled directly from the media renderer.
  • the PA client sends a SIP RE-INVITE message towards the media server control application in the ASN to disengage.
  • This case illustrates a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms, and the serving node triggering a handoff procedure to allow RTSP streaming content to be relayed from the PA client to the associated device.
  • the serving node also determines that the content to be delivered to the newly associated device via the PA (relay) requires trans-coding and directs a Media Resource Control Function (MRCF) to establish the trans-coding session.
  • Transcoding can involve, for example, changing the spatial or and/or color resolution of a video stream to take advantage of higher resolution viewing capability on a discovered device.
  • the MRCF responds to the INVITE request with a 200 OK message indicating the selected media in the SDP.
  • the MRCF will also reserve the requested local resources at that time and return the appropriate resource identifiers in the 200 response.
  • the Media Server Control AS controls a trans-coding session and is aware of MRCF capabilities.
  • the MRCF accepts INVITE requests sent from the AS, via the S-CSCF, to dynamically set up the trans-coding configuration.
  • the INVITE sent to the MRCF contains sufficient information to support the RTSP session that requires trans-coding.
  • the MRCF always grants the requests from the AS, unless it has reached its resource limits.
  • FIG. 17 illustrates the steps involved in setting up the MRCF to provide trans-coding for a mobile originated session, where the MRCF is receiving directions from the AS operating as a back-to-back user agent (B2BUA).
  • B2BUA back-to-back user agent
  • the AS can initiate calls/sessions itself.
  • the number enclosed within the square brackets, i.e., the “[x]” notation, is an indicator of a particular SIP dialog.
  • the media renderer device is discovered by the PA, as described in detail above.
  • an RTSP streaming session is initiated from the mobile handset ( 1702 - 1719 ).
  • the Media Server Control AS is aware of the different codec requirements between the PA client in the mobile handset and the newly associated device by retrieving the ME framework parameters reported by the PA when the newly terminal device is discovered and associated.
  • the Media Server Control AS serves as a B2BUA and interacts with the originating UE as usual to establish the dialog.
  • the Media Server Control AS interacts with the MRCF using a third party control model, as defined in IETF RFC 3264.
  • the Media Server Control AS requests trans-coding facilities from the MRCF ( 1720 ).
  • the request includes the appropriate trans-coding requirements and resources to be established.
  • a separate dialog is established from the Media Server Control AS to the MRCF for the PA client.
  • the offer/answer model is used for SDP negotiation between the Media Server Control AS/S-CSCF and the MRCF.
  • the MRCF should always grant the requests from the AS (unless there is a resource problem).
  • the MRCF responds to the INVITE request ( 1721 , 1722 ) with a 200 response indicating the selected codec in the SDP ( 1723 , 1724 ).
  • the MRCF will also reserve the requested local resources at that time.
  • the media from the PA UE is connected at the trans-coding resource at the Media Resource Function Processor (MRFP).
  • MRFP Media Resource Function Processor
  • the selected codec is included by the Media Server Control AS in the 183 response to the UE. (not on Fig.)
  • the receipt of the ACK at the MRCF ( 1725 , 1726 ) triggers the start of the trans-coding session ( 1727 - 1730 ).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A method of controlling and delivering media content from a media server (MS) to a media renderer (MR) utilizing a wide area IMS network for control. The method involves: provisioning a serving node in the IMS network with control point (CP) logic that includes logic to negotiate media content delivery with a least one of an MS and an MR; provisioning a user endpoint (UE) device of the IMS network with control point proxy (CPP) logic that includes logic to negotiate media content delivery and VCR controls to control media presentation; in response to a media content delivery request, invoking the CPP logic and the CP logic to cooperatively negotiate media content delivery between an MS and an MR that uses local wireless or land line connections when possible in order to minimize wide area bandwidth usage.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a reissue of U.S. patent application Ser. No. 11/370,793, filed on Mar. 8, 2006, now U.S. Pat. No. 7,724,753, granted May 25, 2010, which is a continuation-in-part of and claims priority under 35 U.S.C. §120 to the following applications, the contents of which are incorporated herein by reference in their entirety:
    • U.S. patent application Ser. No. 11/166,407, filed on Jun. 24, 2005, entitled Method and System For Provisioning IMS Networks With Virtual Service Organizations Having Distinct Service Logic, now U.S. Pat. No. 7,792,528;
    • U.S. patent application Ser. No. 11/282,924, filed Nov. 18, 2005, entitled IMS Networks with AVS Sessions with Multiple Access Networks, abandoned.
This application is related to U.S. patent application Ser. No. 11/370,594, filed Mar. 8, 2006, entitled “Associated Device Discovery in IMS Networks” filed on even date herewith , abandoned.
BACKGROUND
1. Field of the Invention
The invention generally relates to IP Multimedia Subsystem (IMS) networks and, more specifically, to IMS users that use (perhaps multiple) discovered user endpoint devices.
2. Discussion of Related Art
Commonly deployed wireless communication networks, usually referred to as 2.5G networks, support both voice and data services. Typically, mobile handsets are connected to a Base Transceiver Station (BTS) using a Radio Access Network (RAN) that uses a modulation scheme such as CDMA (Code Division Multiple Access) or GSM (Global System for Mobile communications). The BTSs are connected via fixed links to one or more Base Station Controllers (BSCs), and the BSCs are aggregated into switches called Mobile Switching Centers (MSCs). The MSC is connected to the Public Land Mobile Network/Public Switched Telephone Network (PLMN/PSTN), typically through a gateway switch called the Gateway Mobile Switching Center (GMSC). Sometimes the term “core network” is used to collectively describe the MSC, GMSC and associated network elements. Voice traffic uses the so called circuit-switched paradigm of communications in which circuits are assigned, i.e., dedicated, to a call for its entire duration; the voice traffic is carried using Time Division Multiplexing (TDM) switching technology. Signaling traffic uses Signaling System 7 (SS7) typically as out of band circuits.
With the advent of Internet Protocol (IP) networking, IP data service is offered to wireless clients by an overlay data network in which a packet control function (PCF) is introduced at the BSC level to connect BSCs to an IP-routed network. The PCF is responsible for packetization of RAN traffic. On the inbound side (core network to RAN) the PCF takes IP packets and reorganizes them for transmission as frames over the radio transport protocol. On the outbound side (RAN to core network) the PCF packetizes radio protocol frames to IP packets. Data connections are handled by this overlay network and the MSC is used primarily to handle circuit-switched voice calls.
The development of Voice over IP (VoIP) technology has resulted in the MSC being re-designed to handle packet-switched voice traffic along with existing circuit-switched traffic. This new architecture is called a soft switch network. The legacy switch is disaggregated into a control and multiplicity of media gateway (MGW) components. The control component (sometimes called the soft switch) uses an open control protocol called the Media Gateway Control Protocol (MGCP) to manage the MGW. The MGW itself has the ability to accept both packet and circuit-switched traffic and convert one to the other, under the control of the soft switch. It is thus possible in 2.5G networks to carry both circuit-switched and packet-switched traffic.
It is widely believed that wireless communications will soon be dominated by multimedia services. This has resulted in new RAN technologies and the resulting networks are called 3G networks. The transition of 2.5G to 3G networks emphasizes packet traffic and new architectures have been proposed to handle multimedia sessions, such as Quality of Service (QoS).
A defining characteristic of 2.5G/3G multimedia services is that since the handset can send or receive IP data packets at any time, the IP context of the handset is maintained as long as the handset is powered on and connected to the network. This is in contrast to traditional telephony where the state of a connection is maintained only while a telephone call is in progress.
In particular, in 3G networks the services are to be provided by so-called Application Servers. Consequently the connection between the service logic and the application server is a “stateful” connection that needs to be maintained for the duration of the service being used. Hence a very large number of stateful connections need to be maintained between the application server complex, hosted in the application domain, and the service logic complex hosted in the service logic domain, in a network servicing a large number of subscribers. Such stateful connections that cross administrative domains have high networking costs and are difficult to maintain operationally.
Typical of proposals for 3G network architecture is the IP Multimedia Subsystem (IMS) architecture, shown in FIG. 1. IMS is independent of the type of access network; that is, it applies both to wireless and landline networks. Examples of access networks include various flavors of Wi-Fi networks, GPRS, and HSDPA networks. IMS uses Session Initiation Protocol (SIP) for control and signaling messages. SIP is an IP-based signaling protocol designed for multimedia communications. The IMS architecture introduces several control functions, i.e., functional entities, to manage the network. The legacy circuit-switched traffic is handled by an Inter-working Function called the BGCF (Breakout gateway control function). The MGW is controlled by a new function called the Media Gateway Control Function (MGCF), and the media processing functions are performed by the Media Resource Function Processor (MRFP), which is controlled by the Media Resource Control Function (MRCF).
The basic call server called the Call State Control Function (CSCF) is logically partitioned into three functional entities, the Proxy, Interrogating and Serving CSCF.
The Proxy Call State Control Function (P-CSCF) is the first contact point for the handset, also referred to herein as the User Entity (UE,) within IMS and provides the following functions:
    • 1. Forward SIP register request received from the UE
    • 2. Forward SIP messages received from the UE to the SIP server
    • 3. Forward the SIP request or response to the UE
    • 4. Detect and handle an emergency session establishment request
    • 5. Generate Call Detail Records (CDRs)
    • 6. Maintain Security Association between itself and each UE
    • 7. Perform SIP message compression/decompression
    • 8. Authorize bearer resources and QoS management
The Interrogating CSCF (I-CSCF) is mainly the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. It provides the following functions:
    • 1. Assign a S-CSCF to a user performing SIP registration
    • 2. Route a SIP request received from another network towards the S-CSCF
    • 3. Obtain from Home Subscriber Server (HSS) the Address of the S-CSCF
    • 4. Forward the SIP request or response to the S-CSCF as determined above
    • 5. Generate Call Detail Records
The Serving CSCF (S-CSCF) actually handles the session states in the network and provides the following functions:
    • 1. Behave as SIP Registrar: accept registration requests and make its information available through the location server
    • 2. Session control for the registered endpoints' sessions
    • 3. Behave as a SIP Proxy Server: accept requests and service them internally or forward them on
    • 4. Behave as a SIP User Agent: terminate and independently generate SIP transactions
    • 5. Interact with application servers for the support of Services via the IMS Service Control (ISC) interface
    • 6. Provide endpoints with service event related information
    • 7. Forward SIP message to the correct CSCF
    • 8. Forward the SIP request or response to a BGCF for call routing to the PSTN or CS Domain
    • 9. Generate Call Detail Records
The P-CSCF is the first point of contact for a UE (handset) in an IMS network. The I-CSCF then helps in establishing which S-CSCF “owns” the UE.
FIG. 2 is a signaling diagram, showing the call flow for a UE when it first establishes contact with an IMS network. The UE sends a “register” request to the proxy (201, 202). Assuming the proxy determines that the UE is registering from a visiting domain, it queries the DNS to find the I-CSCF in the UE's home domain (203). The proxy then sends the registration information to the I-CSCF (204). The HSS checks if the user is already registered and sends the address of the S-CSCF in response (205, 206). An authentication process now ensues in which the UE is challenged to provide valid authentication vectors (207-211). Once the authentication procedure is completed (212-218), the S-CSCF informs the HSS that the UE is registered (219-225).
The HSS provides initial filter codes (IFCs) to the S-CSCF. The IFC, in effect, maps the service codes with various application servers (ASs). Thus, if the UE later issues a service request or if the service is otherwise triggered the mapped AS will be invoked. The IFC is effectively the “call model” for the UE. These call models are static objects downloaded during registration from the HSS. Every UE in the domain of the S-CSCF will, if they have the services enabled at all, have the same application servers (ASs) mapped to the same services. For example, push-to-talk service for each and every UE having such service will point to the same AS or point to an AS with identical service logic to provide the identical push-to-talk functionality.
Registered UEs may use services by initiating a new session establishment procedure depicted in FIG. 3. The Figure shows a session establishment request originating with a S-CSCF (called O-SCSCF) or I-CSCF (called O-ICSCF). This request is routed to the “terminating” S-CSCF (T-SCSCF), which consults the callee's service profile (301). Based on the service profile of the originating registered user, the T-SCSCF sends an IMS service control request (ISC) to the corresponding application server (T-AS) that can handle this service request (302). The T-AS provides the service to the callee and terminates the session (303) and the S-CSCF terminates the application activation process (304).
As an illustrative example, consider the case of voice mail in which callers to a certain user may leave a voice message if the called user does not respond to the call. This voice mail service is provided by an application server (AS) dedicated to this service and having service logic to provide such functionality. The S-CSCF transfers control to the voice mail application server when a certain service point trigger (SPT) occurs, i.e., an event occurs that causes a trigger within the SPT to “fire.” The IFCs that provide trigger points to the service logic of the S-CSCF are downloaded into the S-CSCF during user registration at session initiation time and remain fixed for the duration of the session. The service profile described above that is consulted by the T-SCSCF is a static object in the sense that the information contained in it is defined once at the time of service inception.
The coverage area of a service provider is typically partitioned into geographical regions called cells. Each cell is served by a BTS, i.e., the BTS radiates energy within a cell. Allocating frequencies to cells in a judicious manner allows re-use of frequencies and, hence, to more efficient use of the operator's spectrum allocation. As a mobile handset roams across cell boundaries, its reception of the signal being radiated by the BTS varies. A crucial component of wireless communication networks is the ability to hand off a moving handset from one BTS to a neighboring BTS. Various handoff algorithms are known in the literature. Broadly speaking, all handoff technologies fall into one of two types: hard handoff, and soft handoff.
In hard handoffs the connection between the current BTS and the handset is severed and a new connection is established between a new BTS and the handset while a telephone call is ongoing. The decision to sever the old connection and start a new connection is based on a pre-determined threshold value of the received signal. In soft handoff technologies the signal strength from two (or more) BTS are compared and the one that has the higher value is selected. The main advantage that handoffs provide is that ongoing calls remain connected as the handset roams in the coverage area. Since the region in which a BTS radiates is limited, a handset that roams out of the range of a BTS will lose connection with the BTS and hence any ongoing call will be dropped. Handoffs ensure that the handset remains connected to some BTS and any ongoing calls do not get dropped.
As the bandwidth provided by wireless networks increases, it is now possible to send and receive multimedia information to handsets. Thus, handsets are no longer used only to make and receive telephone calls. Rather handsets are envisioned to send and receive multimedia information such as video clips, audio files, etc. Handsets have become general purpose computing and communication devices. Wireless networks are now expected to provide broadcast content, video telephony, multimedia conferencing, video streaming services, file upload and download services, and interactive multimedia services.
However, the availability of network coverage supporting multimedia services is highly uneven. In some areas several networks may be available simultaneously that could be used by a handset, whereas in other regions there may be insufficient coverage to support a given network service. For example, at a given location one may have several short-range Wi-Fi or WiMax networks, or 1xRTT EVDO, that could provide multimedia services to a handset (assuming that the handset is capable of supporting multiple modulation schemes).
A handset, however, has an inherent disadvantage since its form factor is generally not suitable for long term use as a display device. The small size of the handset display screen is not amenable to long duration sessions or sessions in which the handset is jointly viewed by several users. In such cases it would be desirable to view the multimedia services on a larger LCD or a TV display device. Many such devices support LAN connections directly or indirectly via commercially available media plugs. Moreover, such devices may also support short range wireless networks such as Wi-Fi and WiMax.
The wireless world is increasingly becoming a world of multiple networks. Some are short range and others support longer ranges of coverage. The information-carrying capacity of these networks varies widely from network to network. Handsets increasingly support multiple wireless connections, including both short range networks such as Bluetooth and Wi-Fi, and long range cellular networks.
SUMMARY
The invention provides systems and methods for implementing digital home networks having a control point located on a wide area network. The control point may be implemented on a serving node connected to the wide area network, and have the capability of working in conjunction with one or more control point proxies that are located in handsets connected to a 3G wireless network, or in remote control units located within the home. The control point and control point proxies cooperatively negotiate media delivery from a user-selected media server, such as a home stereo or DVD player, to a user-selected media renderer, such as a TV display or the display on a handset. The control point proxies also include VCR controls for controlling the presentation of the selected media delivery.
In general, in one aspect, the invention features a method of controlling and delivering media content from a media server (MS) to a media renderer (MR) utilizing a wide area IMS network for control. The method involves: provisioning a serving node in the IMS network with control point (CP) logic that includes logic to negotiate media content delivery with at least one of an MS and an MR; provisioning a user endpoint (UE) device of the IMS network with control point proxy (CPP) logic that includes (i) logic to negotiate media content delivery with at least one of an MS and an MR, (ii) logic to cooperate with CP logic to negotiate media content delivery between an MS and an MR, and (iii) VCR controls to control a presentation of content provided by the MS and rendered by the MR; in response to a media content delivery request, determining a network context of the UE and a network connectivity of the MS and MR; invoking the CPP logic and the CP logic to cooperatively negotiate media content delivery between an MS and an MR if one of the MS and MR are not in communication with the UE via a local wireless network; and once media content delivery is negotiated, controlling a presentation of delivery via the VCR controls on the UE.
Other aspects include one or more of the following features. The CPP logic is invoked to negotiate media content delivery between an MS and an MR if the MS and MR are both in communication with the UE via a local wireless network. The local wireless network is a Wi-Fi network, a WiMax network, or a Bluetooth network. The CP logic is invoked to negotiate media content delivery between an MS and an MR if neither the MS nor the MR are in communication the UE via the local wireless network. The UE may be implemented on a handset, and the handset may include a display that is used as the media rendering device. At least one of the MS and the MR is on a 3G network and in communication with the serving node. The UE is in communication with the MR or with both the MS and the MR via a local wireless network. The CP logic negotiates service delivery from the MS, the MS being on a 3G network, the CPP logic in the UE negotiates delivery on the MR, and the CP logic and CPP logic execute synchronization logic to complete the negotiation of delivery from the MS to the MR. The UE communicates its network context to the serving node and the serving node informs the UE of the serving node's capabilities for negotiation with devices local to the UE. The CP logic is configured to serve multiple unrelated devices running CPP logic; these devices can be handsets and remote control units. The principal CPP can depend on the location of the user; for example, the user may use the CPP logic in the handset when the user is remote from the MR and use the CPP logic in a remote control unit when the user is local to the MR. If one of the MS and MR are remote from the UE, the CPP logic provides information about invoked VCR controls to the CP logic on the serving node to allow the CP logic to control the remote MS or MR. The MS and the MR may both be a part of a digital home network. The UE may discover local devices that can act as an MS or an MR by using Universal Plug and Play (UPnP) protocols. The MS and/or MR may announce their presence to the UE using at least one of UPnP protocols, Jini technology, RFID, and Bluetooth. When the CP/CPP is negotiating delivery of media content, it may negotiate of out-of-band media transfer between the MS and the MR.
BRIEF DESCRIPTION OF THE FIGURES
FIG. 1 depicts a prior art IMS network.
FIGS. 2 and 3 are signal diagrams for a prior art IMS network.
FIG. 4 is a block diagram showing the principal elements of the described method.
FIG. 5 depicts logic for providing per user (or group) call models.
FIG. 6 depicts internal architecture of a certain embodiment of the invention.
FIG. 7 depicts logic for providing dynamic call models.
FIG. 8 is a simplified network diagram to illustrate the interaction between a UE, a CSCF and an application server.
FIG. 9 is a simplified network diagram to illustrate the interaction between a UE, a CSCF, a dynamic network topology database (or ME database) and policy database.
FIG. 10 depicts utilization of multiple access networks in a session having an AVS structure.
FIG. 11 depicts out-of-band mediation by a control point to use a potentially non-IMS service in an IMS context.
FIG. 12 depicts out-of-band mediation by a control point and a control point proxy to use a potentially non-IMS service in an IMS context.
FIG. 13 is a flowchart illustrating how devices and services are discovered and associated by the UE.
FIG. 14 is call flow diagram depicting the discovery of a device by a UE.
FIG. 15 is a call flow diagram depicting the discovery of a device by a UE and subsequent handoff to the device.
FIG. 16 is a call flow diagram depicting the discovery of a device by a UE and the establishment of a relay session to stream content to the device.
FIG. 17 is a call flow diagram depicting discovery of a device by a UE and subsequent streaming of trans-coded information to the device.
DETAILED DESCRIPTION
Preferred embodiments of the invention permit IMS user sessions to utilize devices that are discovered by the UE during the course of an IMS session. The embodiments provide for the discovery of available devices, and for choosing whether to add a discovered device to the IMS session. The choice can be made to depend on physical and/or technical factors, such as whether the IMS session involves the use of content that could benefit from the incorporation of the associated device into the IMS session. For example, if the user is receiving video, and a large-screen TV set is discovered, it would be beneficial for the user to view the video on the large screen of the discovered TV set rather than on the small screen of a handset. In addition, the decision to include the discovered device can be made to depend on a set of policies that involve business relationships (such as of the user to owner/operator of the available devices) and cost. The described embodiments allow the signaling channel to remain intact (i.e., it is not generally handed over to an associated device) allowing for a consistent service experience (i.e., the application logic can remain in the domain of the original service provider).
FIG. 4 depicts relevant portions of an IMS network according to preferred embodiments of the invention. The relevant portions include UE 402, P-CSCF 404, I-CSCF 406, serving node 408, HSS 422, and call model database 416.
The UE, P-CSCF 404, I-CSCF 406, and HSS are essentially conventional, though the content of HSS 422 is not, as described below. However, in certain embodiments, the UE may have unconventional agent logic, namely PA logic 424, and search module 426, each of which is discussed in more detail below. All of these entities communicate using known and defined protocols.
Serving node 408, in preferred embodiments, includes S-CSCF logic 410 that is largely conventional though it includes certain modifications, discussed below. Serving node 408 also includes ME server logic 412 (more below) to store users' dynamic network topologies and other information, and provisioning logic 414 more below. (Alternatively, the ME server logic and the provisioning logic may each be a separate physical entity like an AS.) The ME server and provisioning logic essentially are co-located special purpose servers within node 408. The serving node 408, and particularly provisioning logic 414, communicates with a call model database 416. This database 416 (not the HSS as is the conventional case) is used to provide the call model information for a given user (more below).
Though not shown in FIG. 4, serving node 408 communicates with application servers (ASs) that include service logic for various services, e.g., voice mail, push-to-talk, etc. The UEs use predefined codes within service requests to identify the service of interest and/or these services can be triggered in known specified ways via SPTs (as is the conventional case).
FIG. 5 depicts the logic flow for provisioning a S-CSCF with distinct call models for each user. Under preferred embodiments, the HSS provides initial filter codes (IFC) during UE registration (as is the conventional case). However, under certain embodiments of the invention, this IFC is programmed in an unusual way. All the service point triggers (SPTs) for each service are mapped to provisioning logic 414 (i.e., not to ASs corresponding to the actual service codes as is the conventional case.)
The logic flow starts in 500 and proceeds to 502 in which the first service request is received after registration. Because of the default IFC, this service request will not trigger an AS corresponding to that service, and instead will trigger activation 504 of the provisioning logic 414. The provisioning logic 414 will then access 506 the call model database 416. One of the input parameters will identify the user. The call model database 416 will retrieve a call model for that particular user. This call model will include the AS identifiers for the various services for that user. The database 416 will provide 508 the call model information to the provisioning logic 414 which in turn will provide it to the S-CSCF logic 410 within serving node 408. The S-CSCF 410 will construct a new set of filter codes, i.e., NFC, and thus a new call model, for that user (and will trigger the service requested initially using the NFC). The NFC will have SPTs identifying the corresponding ASs. This approach allows for dynamic construction of the NFCs (e.g., post registration) and allows the call model (e.g., NFC with associated SPTs) to be constructed uniquely for each user.
The above logic allows each user to have a call model and NFC that can differ from all other call models served by that S-CSCF. This functionality may be used in many ways. Per-user differentiated call models is useful though not strictly necessary to practice preferred embodiments of the invention.
This form of per user call model customization, in which different users may invoke different service logic functionality for the same given service request, is not provided in a conventional IMS network. In conventional IMS arrangements, the HSS provides static call models at UE registration. Each user gets the same ASs within their IFC and thus the same service experience (for services they are authorized to use). Moreover, the above approach allows for full portability of call models. No matter where a UE exists in the IMS network, that UE's call model may be constructed and used for that UE's service experience.
FIG. 6 depicts serving node 408 once multiple users have registered and been provisioned with their corresponding call models 602a . . . n. Note, the different call models can point to different ASs for a given service, and they are not merely multiple instances of the same IFC/call model. Multimedia network manager 606 receives service requests 608 from the IMS network and provides service responses 610 to the IMS network. It also routes received requests to the appropriate internal entities as shown. ME server logic and Network Map policy manager 412 are responsible for receiving information (more below) indicating that the user's UE environment has changed with new capabilities or devices, and for building information structures and models to reflect these capabilities. In certain embodiments it also includes logic to implement specified policies on whether and how to utilize such capabilities. Provisioned Service logic 414 is responsible for interacting with external or internal databases (e.g., database 416 of FIG. 4). Media resource manager 612 is responsible for managing other resources (e.g., transcoders) that may be involved with a given service. Multimedia service manager 604 is responsible for receiving requests from network manager 606 and for interacting with the other components to construct and build the per-user call model 602. In simple cases this may involve creating call models with the help of the provisioning logic 414 and call model database 416. In other cases the call model construction will be dynamic (more below) using new devices and capabilities (as well as associated policies), and in these instances the manager 604 will involve ME logic 412, media resource manager 612 as well as handoff control application server 614.
The term handoff as used herein denotes the transfer of a service delivery from one network and/or device to another network and/or device. The handoff does not involve the dropping of an access network connection. This meaning contrasts with the meaning of the term that often appears in the prior art (referred to in the background section above), in which handoff means the dropping of a first connection in favor of a second connection based on the relative signal strengths of the two connections.
The context of an end user may change. For example, as a user roams, his or her context may change. Alternatively, even in non-roaming situations, the user context may change as new devices and capabilities emerge or become activated.
At any given moment, the user may be in close proximity to any number of devices that are capable of acting as a UE for a certain service (application). For example, the user may be near a TV that could be used to display multimedia content. Or the user may be in close proximity to a personal computer that could be used to receive multimedia information from a network connection, provided network connectivity and authorization to use such a device in this manner could be obtained.
The described methods allow a roaming user to discover (directly or indirectly) several kinds of information and invoke several kinds of corresponding relevant policies to consider when and how to use such capabilities and devices:
    • 1. New endpoint devices (UEs or UE devices) that could be used to receive multimedia information;
    • 2. New network connections that terminate and emanate from the UE devices;
    • 3. New device capabilities;
    • 4. Policies that govern use of newly discovered devices and new network connections; and
    • 5. Policies that are implemented by the service provider that control what devices could be used for which type of services under what sort of conditions.
Policies may reside either in the UE or in a designated server in the network. In a preferred embodiment, the policies reside in the network.
An increasing number of mobile handsets support short-range wireless technologies such as Bluetooth and Wi-Fi. According to certain embodiments, a “dynamic profile” is constructed, in part, by logic that executes in the handset. This logic may be executed continuously, periodically at some network determined time interval, or on demand when the user requests a particular service. When executed, the logic senses (or otherwise discovers) the presence of associated devices in the immediate vicinity of the handset using a short-range wireless technology such as Wi-Fi.
Home and personal networking systems increasingly feature the ability to discover new devices using so-called discovery protocols. One such example is the Universal Plug and Play (UPnP) protocol that allows the dynamic discovery of devices. According to certain embodiments, dynamic device discovery and service discovery framework within a user's personal or home area network is performed. For example, UPnP may be used to create a dynamic profile of the immediate environment of the handset (i.e., user) service environment. The dynamic device discovery mechanism is used to help create a personalized user area network map, which will serve as input to the switching/delivery logic.
Associated devices may announce their presence by a variety of means such as but not limited to Universal Plug and Play Devices (UPnP), Jini discoverable devices, RFID devices, and Bluetooth enabled devices.
Any method of broadcasting the capability of devices can be used. The sensing logic in the handset receives such broadcast information and assembles it to construct a dynamic profile of the user's immediate context. Since this context changes as the user roams, the dynamic profile changes to reflect the current vicinity of the handset. The dynamic profile is communicated to the serving node 408. For example, this information may be communicated as parameters (e.g., by overloading information elements [IEs] of Session Description Protocol (SDP) messages) in conjunction with a special service request dedicated to communicating potential UE devices.
A personal agent (PA) having PA logic 424 executes in UE (handset) 402 and includes the sensing logic to discover such other potential UEs or associated devices (more below). The dynamic profile of the user's immediate environment is communicated to the ME logic 412. This is done by having the ME server invoked in response to the special service request from the UE for communicating such discovered devices and capabilities. The ME service will construct topologies and maps to identify the potential UEs, other networks, etc., to reflect the new devices and capabilities discovered or sensed in the UE's vicinity that could potentially be used by a given user.
In certain embodiments, the handset's User Agent profile (UAProf) or Composite Capabilities/Preference Profiles (CC/PP) representing device capabilities and user preferences is used to personalize the multimedia service delivery framework. Serving node 408 will gather the UAProf or CC/PP from the endpoint devices to guide control of not only the rendering and trans-coding of content to be delivered to that device, but also the generation of the call agent as well as the decision to execute that service agent within the network or at the endpoint.
The personal agent supports an automated network and service discovery mechanism, such as the industry standard Universal Plug and Play (UpnP) framework, to establish association with and control of those networked devices. The networked devices that the PA can be associated with through the discovery procedure can be connected to the mobile handset via wireless connectivity, such as Bluetooth, Jini, self-identifying label technologies such as RFID, or Wi-Fi, or via wired connectivity, such as USB or IEEE 1394 links.
In certain embodiments, the static user profile downloaded by the HSS into the S-CSCF at registration time is provisioned by the network operator to contain the address of the ME server. Thus, every communication of the dynamic profile originating from the UE and received by the S-CSCF causes a SPT trigger to fire, and control is transferred to the corresponding ME server. In this fashion the serving node 408 and more particularly the ME server 412 becomes aware of the immediate context of the UE (handset).
Once the ME server has the information in the dynamic profile, it consults a database of policies described by the service operator. These policy descriptions may be co-located with the ME logic and even the S-CSCF logic (see, e.g., FIG. 6). These policies prescribe certain actions that depend on the data contained in the dynamic profile. For example, a policy can require that if the UE sensing logic discovers a Wi-Fi connection in its immediate vicinity, then this discovered network should be used for originating session requests. Specific logic associated with this policy is then executed to send directions to the PA to enforce this directive at the UE level. When evoked, the policy decision only changes the behavior of those UEs that come under the control of a particular Mobile Virtual Network Operator (MVNO) (A MVNO is an operator that use the radio spectrum license-holder's underlying network facilities to offer services to the consumer. MVNOs do not typically own network infrastructure or spectrum license). Another MVNO may, in general, have a completely different set of policies. Policies may not only be specified by the MVNO but also by end users, provided the network interfaces allow the users to specify actions that should be taken when certain events and situations are discovered in the UE's environment. Such user specified policies may over-ride policies specified by the MVNO.
FIG. 7 is a flow diagram illustrating the customization of service logic. The logic starts in step 700 and proceeds to step 702 in which the PA logic 424 on the UE discovers or senses its immediate environment or context and constructs a message specifying this dynamic context. This message may include information about, new devices that could be used to receive multimedia information, new network connections that terminate and emanate from such devices, and new device capabilities. The PA on the UE sends the message to S-CSCF (704) and the message either causes an SPT trigger or it does not, depending on how the IFC or NFC is constructed (706). If the message is triggering event, the logic proceeds to step 708 in which control is transferred to the ME server; otherwise the logic terminates (799). The ME server updates its internal database to reflect the information communicated in the message from the PA in the UE (710). The ME server then applies any relevant policies that will determine, for example, whether and how to utilize newly discovered devices and capabilities (712), and the logic determines whether any action is specified by the policy (714). If so, the specified action is initiated (716). This can be done by customizing the PA logic 424 on the UE or by customizing the AS logic. For example, in a typical embodiment, S-CSCF logic 410 will be modified to initiate or trigger the specified actions after the ME logic has updated its models accordingly and perhaps after a new dynamic call model is instructed for that particular user to reflect new devices and capabilities.
In an alternative embodiment S-CSCF logic 410 is not hosted within a serving node 408 as shown in FIG. 4; that is, the S-CSCF 410 is not constrained to be hosted by the MVNO domain. In this embodiment the S-CSCF remains hosted in the IMS serving domain of the network operator and is a separate entity, as in a conventional IMS network, and the ME server and provisioning logic are configured as ASs, though, as explained above, they do not provide conventional IMS services and instead are used in the construction of dynamic call models.
The interactions between the CSCF and an AS are summarized in FIG. 8. As outlined above, in IMS networks, all services are provided by application servers (ASs). In FIG. 8, the network is simplified (for descriptive purposes) to show only one AS 802, but in practice there will be multiple ASs. Service requests are sent (directly or indirectly) from a UE 402 (see also FIG. 4) to a S-CSCF 410 (see also FIG. 4). The S-CSCF uses its internal call model (see, e.g., 602 of FIG. 6) to invoke a corresponding application server.
In preferred embodiments, the call-model 602 (FIG. 6) (i.e., state machine) executing in the S-CSCF 410 for this UE is modified to take into consideration the newly discovered devices and network connections as described herein. This newly discovered information is stored in the ME server 412. The discovery is done by sensing logic resident in the UE and may be communicated to the ME server periodically, or when discovered, or at pre-designated intervals. As discussed above, this communication may be done, for example, by overloading the information elements of the SDP. The interaction between the ME server 412 and the CSCF 410 is shown in FIG. 9. As described above, the CSCF 410 is invoked with messages (or overloaded messages) that include information about discovered devices, network connections, new capabilities, etc. The CSCF 410 then invokes the ME server 412 which in turn consults the policy database 902.
In one scenario, a subscriber wanting to view multimedia content from an Internet server on his handset initiates an IMS request to serving node 408. The request emanates from the UE to the P-CSCF and onwards to the S-CSCF as explained above in connection with FIG. 1. From the S-CSCF it is routed to the ME (acting as an Application server) so as to perform per subscriber customization, as explained in connection with FIG. 4. This request then causes a connection to be made to the serving node 408 (explained in more detail later) and an IMS session is established between serving node 408 and the UE using the access network to which the P-CSCF is attached. This IMS session is uniquely identified by an IMS Charging ID (ICID) assigned by the P-CSCF.
As shown in FIG. 10, PPP (Point to Point Protocol) session 1002 has its own unique identifier called the Transport Charging ID (TCID) 1006 assigned by the device (Packet data Gateway or Packet Control Function in the BSC) from which the PPP session emanates. TCID 1006 and ICID 1008 together uniquely identify the multimedia session in which the SIP/IMS signaling is embedded within the IP/PPP connection.
The ME function 412 creates or modifies a computational entity called an AVS (Audio Video Session) 1004 to model and control (in part) the actual access network connections for a given user. The call model 602a, discussed previously, is constructed first, based on the resources and policies. The AVS, on the other hand, represents what is actually going on, or intended to take place, or actually takes place (i.e., dynamically modifying to context). That is, the AVS represents the actual connections registered or to be registered in response to a given service request. If each access network connection is considered to be a “session”, then the AVS is a form of meta-session, or a super-session incorporating the access network sessions. Each AVS is uniquely identified by a AVID (Audio Video session ID) that is a function of the underlying TCID and the ICID.
An AVS is a representation of every access network that the UE encounters while roaming. For each new access network this representation creates a new “leg” (called Incoming Call Leg-ICL 1012, 1014). Each ICL has associated with it a TCID and an ICID (generated by other network elements) that together uniquely identify the session corresponding to that access network. Since the AVS 1004 has access to registration information of the UE, it knows that various ICLs (and hence various TCID+ICID combinations) really belong to the same UE, and hence, for each UE, the AVS representation captures all the access networks that the handset encounters. And since some access networks may support circuit-switched (CS) transport mode whereas others may support packet-switched (PS) transport modes, ICLs may be CS or PS supporting ICLs.
Network policies (see FIG. 9) will generally govern the co-existence of ICLs within a single AVS. For example, current telecomm networks do not support the idea of a UE being associated with more than one circuit-switched network. This translates into an AVS constraint: “only one ICL may exist for CS sessions.” Another example of a constraint is provided by current so-called Class B handsets in which both a CS and PS protocol stack are available but only one such stack can execute at any time. Yet another example is provided by Class B+Wi-Fi handsets in which a CS session and a Wi-Fi session, or a Wi-Fi and a PS session can coexist. In a Class A handset that supports CS, PS and Wi-Fi contemporaneously, all three sessions can be active together. Such constraints, emanating from the network or the handset, translate into constraints on the type and number of ICLs can be supported by an AVS. The policies can be contained in the policy database, and as with the construction of call models, the policies may be accessed when modifying AVSs.
In one example, a class B UE is engaged in a PS session watching Mobile TV. The UE roams into a Wi-Fi zone and a handoff happens, after which the MobileTV feed uses the Wi-Fi network. The previous PS session is idle and could be cleared. However, keeping it around serves a useful purpose. For example, suppose a voice call arrives for this UE. Since the CS stack is not executing in the UE, the call will normally be routed to voice mail without the user being informed of the call. But suppose a serving node 408 is informed of the arrival of this call (as explained below), and then uses the PS session to present a dialog box giving the user a choice to take the voice call. This example shows the usefulness of having more than one session (more than one ICL) active. Policies governing a given service will dictate whether or not to keep a leg active. Moreover, sometimes a leg may be unavoidably dropped, for example via lack of sufficient use, or because of signal issues.
As stated above, the serving node 408 includes one AVS per user. As shown in FIG. 10, an AVS 1004 can include multiple ICLs 1012, 1014 and an OCL or OGL 1010 (outgoing call leg). The AVS also includes a control point 1016. As explained below, the control point (CP) may be used to provide mediation between some form of service or server and the UE. Not shown in FIG. 10 is that each leg may have effectuation routines to perform or effectuate routine functions on a given access network, such as responding to “are you alive” messages. When the serving node 408 (e.g., via the ME logic) manipulates the AVS it corresponds to actions in the “real world.” For example, adding an ICL means getting registered on that access network.
FIG. 11 illustrates how certain components, particularly the CP 1016 interact with other entities. It also shows how to incorporate non-IMS (legacy) services into a network, or to “marry” multiple networks. As explained below, the CP 1016 within AVS 1004, can perform out of band mediation so that a media server (MS) 1104 somewhere in the network can deliver content to a media renderer (MR) program 1106 on the UE, which receives and presents such content.
CP 1016 is connected to the MS 1102, which in turn establishes a connection to the serving node 408 (using network server specific protocols). The connection between the CP and the MS is internal to the ME 412. The connection between the MS and the serving node 408 is an Outgoing Leg 1010 of the AVS. That is, AVS 1004 models this connection as outgoing leg component 1010. CP 1016 is also connected to MR 1104, which preferable may reside in the UE. The connection between the CP and the MR is an Incoming Leg, e.g., 1012. That is, AVS 1004 models this connection as incoming leg component 1012 or 1014. Thus, in a session having multiple MRs there are multiple Incoming Legs for a single AVS, as shown in FIG. 10.
Continuing with the example above, the CP negotiates multimedia content delivery with the MS and instructs the MS to deliver content to an address corresponding to the MR on the UE. The instructions provided during such mediation will conform to the environment, context, and capabilities of the UE. CP 1016 also negotiates media rendering with the MR itself in each Incoming Leg of the AVS. That is, the CP effectively instructs the MR to start expecting content from the MS, and to present such. Again, the instructions provided during such mediation will conform to the environment, context, and capabilities of the UE.
When an access network connection is discovered by the UE sensing logic and communicated to ME server 412, and if the policy database 902 (FIG. 9) permits its use, the newly discovered access network connection is modeled and included into the current AVS as an Incoming Leg. Each access network available to a UE corresponds to an Incoming Leg of an AVS and the connection between the CP and MS corresponds to the Outgoing Leg of the AVS.
Thus, if the UE has sensed three different access networks and policy allows all three, then there are three distinct access network connections between the UE and the S-CSCF. In such a situation, there are signaling and bearer channels in each access network that can be utilized. It is a matter of policy that decides which signaling channel within an access network is to be used and which channels within an access network is to be used for bearer traffic. In the case when coverage of an access network is lost (for example, due to roaming of the UE), the corresponding access network connection and the associated AVS Incoming Leg is “cleared” under S-CSCF serving logic control by the P-CSCF.
As mentioned above, many new kinds of access networks, such as Wi-Fi and WiMax, are being deployed. The proposed IMS specifications allow the UE to connect to an access network. Preferred embodiments of the present invention allow the UE to remain in simultaneous connection (or potential use) with multiple access networks and the choice of which access network to deliver a particular service to the UE is to be made by policies resident in the ME function in the serving node of the network. That is, the AVS facilitates control of multiple access networks (both signaling and bearer) and allows choices to be made (by the system and perhaps the user) as to which network to use in a given context and time.
In conjunction with deployments of various kinds of access networks, handset manufacturers are also producing handsets that support multiple radio access technologies. Examples of such handsets today are those that support Wi-Fi and GSM/CDMA cellular networks. In such handsets, known as Class A handsets, both the circuit-switched session of the GSM/CDMA network and the packet-switched session of Wi-Fi can co-exist and be active simultaneously. Moreover, there are numerous proposals for voice call handoffs between cellular (GSM/CDMA) and Wi-Fi networks.
Using the described embodiments, a Class A handset can have multiple packet sessions and a circuit-switched session simultaneously active in the handset. In the terminology explained above, the corresponding AVS may have multiple Incoming Legs corresponding to one circuit-switched and multiple packet-switched sessions. Another type of handset, called a Class B, handset only supports either a circuit-switched session or a packet session at any given time. If the handset roams into a Wi-Fi area from a cellular area, the circuit-switched session is replaced by a new packet-switched session supported by the new Wi-Fi network in a Class B handset; in a Class A handset the circuit-switched session can be allowed to persist. This corresponds to removing one Incoming Leg of the AVS (representing the circuit-switched cellular connection) and adding another Incoming Leg (representing the Wi-Fi connection) to the underlying AVS for Class B handsets. In the case of Class A handsets in which the circuit-switched session is not cleared, the situation corresponds to simply adding another Incoming Leg to the AVS session.
The following scenarios for Class A and B handsets are possible:
    • 1. Two subscribers A and B are in a voice call. The AVS corresponding to this call for A's UE may have an Incoming Leg (circuit-switched) for A. The AVS for B's UE has an incoming leg (“packet-switched”) for B. Thus, A is engaged in a circuit-switched call and ‘B’ is engaged in a packet-switched call; the two parties in the call are using different access technologies. This example extends to multiparty calls.
    • 2. Two subscribers A and B are in a voice call. Both users are assumed to be using packet-switched sessions (i.e., packet-switched [PS] modulation over the cellular spectrum). Under roaming conditions, at some point in this call, assume that both roam into new access networks that offer the resources (e.g., bandwidth) to support a video telephony sessions between A and B. These new access networks will correspond to new Incoming Legs added to the AVSs, along with new media renderers, and the policy in ME will dictate the use of the new access networks to support the video call. The new media renderers for the video telephony will be OCLs for each of the AVSs—i.e., AVS for A and an AVS for B.
    • 3. Two subscribers A and B are in a voice call. Assume that A is in a circuit-switched session and that B is in a packet-switched session. Now assume that A roams into a new access network such as Wi-Fi that supports video telephony. This new access network corresponds to a new Incoming Leg of the underlying AVS for A. The AVS under policy control may now be, as in use case number 2 above, converted into a video telephony session. An OCL may be added to correspond to a new OCL for the MR for the delivery of video telephony.
    • 4. Two subscribers A and B are in a circuit-switched voice call. A now wishes to send a multimedia message including images to ‘B.’ Assume that both A and B had previously roamed into new access networks that correspond to packet-switched sessions (Incoming Legs) in the underlying AVS for each. These packet-switched sessions can be used to deliver the multimedia object from A to B.
Scenarios 1-4 show that by having access to multiple access networks under mobility situations, the described embodiments allow services that use a combination of packet and circuit-switched access network technologies.
As explained above, mechanisms to utilize non-IMS, legacy services within an IMS context are provided. To do this, the system logically separates the control and bearer parts of the legacy service. The control component of the service is handled by IMS, and the bearer component may remain independent of IMS. The control point (CP) 1016, referred to earlier, is the mechanism used to allow “out of band” media transport under control of IMS. Under preferred embodiments every AVS 1004 has an associated CP 1016, for example, logically within the AVS. More specifically, each AVS is designated to have an “Outgoing Leg” (OCL) 1010 that contains a CP. The CP has capability to transact with an Application Server (AS) using a standard protocol, such as RTSP, and it has the capability to transact with programs in the UE called Media Renders (MRs), again using standard protocols such as SIP, or SOAP/HTTP. The CP itself may be considered an Application Server (AS) by the S-CSCF (i.e., interacted with as if it were an AS).
Now consider a UE requesting Mobile TV service. This request emanates from the UE (on an ICL) and is forwarded by the S-CSCF to the CP 1016 acting as an AS (in standard IMS fashion). Since the CP acting as an AS has access to IMS charging and authentication mechanisms, the first objective of re-using IMS infrastructure for legacy services is fulfilled. Once the charging and various other bookkeeping functions have been finished, the CP contacts the MobileTV server (e.g., illustrated as Content Server 1018 in FIG. 10) using RTSP protocol. Alternatively, the CP could pass control to another Application Server that now contacts the MobileTV server using RTSP″, i.e., there is a chain of Application Servers as in standard IMS. (Chaining of application servers is a known technique). The CP instructs the MobileTV server to initiate sending media to the UE (at a designed IP address) and instructs the MR in the UE to render the incoming media. (See FIG. 11.) This media transfer from the MS to the MR may use an out-of-band (non IMS) transport such as RTP/UDP/IP. In some situations, other approaches to deliver media will be needed. For example, the MobileTV server may not support the capability of receiving a service request from client A and initiating service to a client at a different address. In this case the MobileTV server will be asked to send the media to the CP's address and it will be forwarded to the UE by the CP, a process called re-NATting).
The communication between the CP and the UE for setting up media rendering and for other functions uses valuable spectrum. In order to reduce such spectrum-consuming communications, the relationship between an MR and a media server can be fixed a priori and pre-provisioned. Thus the CP always picks a pre-designated MR for a particular media server.
In a preferred embodiment, wireless spectrum-consuming communications between the CP, media servers and media renderers are reduced by introducing a CP Proxy (CPP) that resides in the UE. This architecture is illustrated in FIG. 12.
As indicated above, UPnP architecture includes three functional entities: control point (CP), media server (MS), and media renderer (MR). These may be implemented in different physical devices. In a digital home environment, for example, the MS and MR typically reside in a TV set and the CP in a remote control unit.
It is assumed that the MS and MR entities represent abstractions that capture the essence of media servers and media renderers. The abstractions allow programmers to write general-purpose software that deals with the properties of these entities without having to deal with their inner workings. The handling of these inner workings is left to the implementation of the media server and the media renderer themselves. Thus, by way of example, if a program desires to issue a “suspend” command to an MS, it may use the MS's defined interface to issue that command. It is left to the MS to implement the “suspend” command.
Communications between the CP and an MS and MR use the SOAP/HTTP protocols. Direct communication between an MS and an MR is referred to as “out of band,” since is up to the MS and MR to select the protocol. One such protocol is RTSP/RTP.
In one example, the MS implements a video player, the MR implements an LCD display, and the CP implements a remote control unit. The CP queries the MS for a contents directory and presents that on the display unit, allowing content to be selected for rendering. The commands between the CP and MS, and between the CP and MR use SOAP/HTTP. The communication between MS and MR could use RTSP/RTP.
In a wireless network in which the CP implements a handset, and the MS and MR implement a non-mobile media server and media renderer, the wireless network could be used to carry a control protocol between the these three entities, akin to SOAP/HTTP (but perhaps a more secure version). However, this approach suffers from the disadvantage that the control messages between the CP and the MS, and the CP and the MR use the limited capacity of the wireless network.
In certain embodiments, the UPnP architecture is extended into a wide area network environment. One approach, illustrated in FIG. 12, reduces control message traffic over the wireless network by moving CP 1016 into a network element and running one or more CPPs 1202 in one or more handset(s). This architecture has two advantages. First, the communication between CP 1016 and MS 1102 need no longer use the wireless network. Second, when CPP 1202 is in close proximity to MR 1104, the handset (CPP) can use an available Personal Area Network (PAN), such as Wi-Fi, to communicate with the MR. Since the wide area wireless network uses expensive spectrum, these advantages can afford considerable cost savings.
In this architecture, the CP and the CPPs need a synchronization protocol. Communication between the CP and the CPP could be optimized by using off-peak times to communicate and by making the CPP as independent of the CP as possible.
Moving the control point into the wide area network enables a user to connect to services provided by MSs that are not located in the home, such as foreign television stations. In addition, MSs, whether in the home or not, can now be rendered on MRs outside the home, such as on the handset itself, or on an MR that is in proximity to the handset running the CPP when the handset is outside the home, as described above.
CP 1016 running in the SN can support multiple CPPs. For example, there can be a CPP implemented in a handset, and also in a remote control unit. When the user is inside the home, he may prefer to use the remote control unit as the CPP since it may have a better form factor for VCR-type controls. On the other hand, when the user is outside the home, he invokes the CPP on the handset in order to maintain connection and control with the home network.
The above techniques are illustrated by the following communication sequence. A subscriber requests a media service to be rendered on a home Wi-Fi-enabled display device. CPP 1202 communicates with CP 1016 via internal interface 1204 using the wide area wireless network. Subsequent communication between CP 1016 and MS 1102, or between CPP 1202 and MR 1104 need not use the wireless network. Upon receiving confirmation from CP 1016, CPP 1202 instructs MR 1104 to negotiate an out-of-band service request with MS 1102.
In the case where the UE is in the proximity of both the desired MS and the desired MR and can communicate with them via a PAN, such as Wi-Fi, the CPP in the UE negotiates the association between the MS and MR. In this case there is no need to involve the CP in the SN, since this would involve unnecessary use of wireless bandwidth. Conversely, when the UE is not in the proximity of either the desired MS or the desired MR, the CP handles the negotiation and association of both the MR and MS, using fixed communication links instead of wireless links.
Thus, in a wide area networking extension of UPnP, moving the CP into a network element, such as the serving node of an IMS session, and placing the CPP into the handset optimizes usage of the wireless spectrum usage.
This architecture also allows normal telephony to be integrated with UPnP-based media services. As used herein, normal telephony includes supplementary features such as call diversion, three-way calling, and voicemail.
In an alternative architecture, the CP does not migrate to the core network, but continues to reside in the handset. In this peer-to-peer style architecture, there is no core network element, but the peer-to-peer signaling uses the valuable and limited resources of the wireless spectrum. The network-based architecture, as indicated above, consumes less wireless spectrum.
CPP 1202 has local service logic that decides what MR to pick for a particular media server. In other words, the CP-MR negotiation is transformed into CPP-MR negotiation (which is local to a UE and hence does not use spectrum). Moreover, the CPP policies and logic can be updated periodically from the network-resident CP at opportune times.
In yet another embodiment, the concept of MVNO-customized logic may be applied to so-called hybrid networks. In general a hybrid network is a combination of two or more individual networks. Examples of digital broadcast networks for joint use are DVB-H (Digital Video Broadcast—Handheld), and Media FLO (Forward Link Only). In a hybrid network, the broadcast network provides a high capacity but one-way transport for multimedia (video) traffic, while the UMTS (Universal Mobile Telecommunications System) network (or other network) may provide lower capacity two-way transport for interactive services. In such hybrid networks, the UMTS network is used for control and signaling purposes for the services offered by the broadcast component network. In this fashion, the UMTS network supplements the digital broadcast network by providing a control network or a network for user interactivity functions. Conversely, the broadcast network may supplement a UMTS (or other) network by providing certain broadcast functionality.
Since the PA runs in mobile handset environment, the handset has a direct logical service interface to the Internet Wide Area Network (WAN) via the 2G/3G wireless network. From the UPnP device architecture perspective, the PA serves as an Internet Gateway Device (IGD). An IGD is an “edge” interconnect device between a residential Local Area Network (LAN) and the Wide Area Network (WAN), providing connectivity to the Internet. The IGD typically runs in the local network environment, e.g., on a PC in the WLAN environment.
In the search process described below, the discovery, registration, and use of an associated device corresponds to the setting up of a new incoming leg of the AVS session. The ME server then determines whether there is an advantage to be gained from switching the media rendering from the renderer in the handset to a renderer in a discovered device. The CPP can then offer a choice to the user as to whether to switch to the new renderer, or the switch can be performed automatically.
A UPnP service manager (SM) is provided in the PA to organize the services discovered, as shown in FIG. 13. The UPnP service manager performs device/service search and also listens to advertisements being sent out by new devices. FIG. 13 illustrates exemplary logic for the service manager. The service manager logic starts (1302) when the PA detects the presence of a PAN. The service manager consults a directory of services that are potentially available on the PAN (1304). If the UE is seeking to use a service, and it finds the service present in the directory, the service manager joins the PAN (1306) and broadcasts a search message (1308). When the PA receives responses from the services on the PAN, it determines whether the user is authorized to use the desired service, and whether the service is still available (1310). If the answer is yes, the process for associating the PA with the new service takes place (1312, 1314, 1316, 1318, and 1320). If the UE is seeking to provide a service in the PAN, and the service is not already present in the PAN (1304), the service manager joins the network (1322) and broadcasts an advertising message (1324). In response, it may receive messages from the devices on the PAN (1326), and then proceed to associate itself with PAN (1314, 1316, 1318, and 1320).
Two functions enable the discovery process: search module 426 (see FIG. 4) running in PA logic 424, and the advertisement module, running in a device to be added to the network.
Search Module
Search module 426 is a UDP-based function in the PA that broadcasts search messages whenever the user wants to search for new devices. It communicates with the user interface of the service manager and updates a list (in the PA logic 424) of discovered devices on the service manager when it finds a new device. It determines whether or not the device is new by matching its Universally Unique Identifier (UUID) against those of the devices already discovered. Each device has a unique UUID.
Search Module 426 consists of the following procedures:
Discovery: The discovery protocol allows control point proxies, such as the PA, to search for devices of interest in the network. A search is carried out by multicasting a search message with a pattern equal to a type or identifier for a device or service. Responses from service providers/devices contain discovery messages that are essentially identical to those advertised by newly connected devices. In other words, the responses to the outgoing discovery messages from the PA are similar to the messages the service providers/devices are themselves unicasting as their own advertising messages, as described below. The former are unicast while the latter are multicast. Below is a format of a Search message:
M-SEARCH*HTTP/1.1
HOST: 239.255.255.250:1900
MAN: ssdp: discover
MX: seconds to delay response
ST: search target
Response: In a response, the discovered device sends a message to the M-SEARCH source IP address and port that sent the discovery request to the multicast channel. This response follows the same pattern as listed for NOTIFY with “ssdp: alive” (see below in the description of the advertising module) except that a search target (ST) header is used instead of the new target (NT) header. The format is as follows:
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=seconds until advertisement expires
DATE: when response was generated
EXT:
LOCATION: URL for UPnP description for root device
SERVER: OS/version, UPnP/1.0, product/version
ST: search target
USN: advertisement UUI
Description: After the PA has discovered a device, the PA still knows very little about the device. In order to learn more about the device and its capabilities, or to interact with the device, the PA retrieves the device's description from the URL provided by the device in the discovery message. The PA sends the following request header to the discovered device:
GET path to description HTTP/1.1
HOST: host for description: port for description
ACCEPT-LANGUAGE: language preferred by control point.
By default the ‘Host’ and ‘Accept’ header fields in the request headers are sent, following normal conventions, such as from HTML. Once the socket is created, where the HostName and RemotePort properties are set to the values specified in the URL, the request header block is then sent to the discovered device, which consists of the command (GET) and the other header fields defined above. A sample of a device description in the XML format is shown:
<serviceList>
<service>
<serviceType>Telephony</serviceType>
<SCPDURL>URL to service description</SCPDURL>
<controlURL>URL for control</controlURL>
<eventSubURL>URL for eventing</eventSubURL>
</service>
</serviceList>
Advertisement Module
When a device is added to the network, it advertises its services to control points by multicasting discovery messages to a standard address and port at regular time intervals. Serving as an UPnP control point, the PA listens to this port to detect when new capabilities are available on the network. Each advertisement message contains information specific to the embedded device or service as well as information about its enclosing device. Messages should include the duration until the advertisements expire. If the device becomes unavailable, the device will either explicitly cancel its advertisements, or wait for the advertisements to expire on their own.
The advertisement module in the PA listens for advertisement messages. It is also a UDP-based application that listens on port 1900 (as given in the UPnP specifications). It communicates with the user interface of the service manager and updates the list of discovered devices on the service manager when it finds a new device. It determines whether or not the device is new by matching its UUID against those of the devices already discovered.
The service manager is needed because more than one service may be present in the Personal Area Network (PAN) and the manager provides an easy and intuitive way for the user to manage all the discovered services/devices. In addition, the service manager is responsible for communicating the updated PAN neighborhood configuration (i.e., context) of the mobile handset to serving node 408. The discovered device and service will be reported to the serving node 408 in a SIP message which includes an SDP extension header. The service manager enables the mobile handset user to accomplish this.
When a new device is added to the list in the service manager a timer is started whose value depends on the cache-expiry value sent by the device. Once this timer expires, the device/service is removed from the list. However, if an advertisement message is received from that device the timer is restarted.
The format of the multicast message is as follows: values in italics are placeholders for actual values.
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
CACHE-CONTROL: max-age=seconds until advertisement expires
LOCATION: URL for UPnP description for root device
NT: search target
NTS: ssdp: alive
SERVER: OS/version, UPnP/1.0, product/version
USN: advertisement UUID
UPnP Device Discovery
The following case illustrates by way of example a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms. In this example, the new device to be associated with the PA client is powered on and starts advertising its service and device descriptions. For example, the new device might be a PC with IGD software, whose display will be used as a media renderer.
As depicted by 1401a, 1401b, and 1402 in FIG. 14, when a device is added to the network, the device is allowed to advertise its presence on the network using Simple Service Discovery Protocol (SSDP). The UPnP discovery procedure operates transparently on top of various wireless or wired PANs or Home Area Networks (HANs), such as Bluetooth, Wi-Fi, USB, etc. When a control point such as the PA IMS/SIP mobile client is added, the control point is similarly allowed to generate a multicast search for devices. In either case, the message exchange consists of a brief description of the device that includes the UPnP device type, the device ID, and a URL to the full device description. The message formats are as described above.
Next, as depicted by steps 1403-1406 in FIG. 14, the UE obtains more information about a specific device by retrieving the full description from the URL with HTTP GET. The full description is composed of a device description and a service description. The device and service descriptions are XML documents and are constructed by the device vendor with the aid of the device and service template schemas. The service description contains details of the hosted API commands, which are called actions, along with parameters, which are called arguments.
As shown by 1407 in FIG. 14, once the device and service descriptions of a particular media device in the PAN/HAN have been retrieved, the PA IMS/SIP mobile client has established an association with that device, completing the UPnP device discovery process.
Associated Device Discovery and Handoff Session Via UPnP
The following case illustrates a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms, and the serving node triggering a handoff procedure from the PA client to the associated device to initiate a real time streaming protocol (RTSP) streaming session. In this example, an IMS/SIP session has been established between the PA and the Media Server Control AS in the serving node.
As depicted by 1501-1507 in FIG. 15, the discovery and association of the new device proceeds as described above. Next, as shown by 1508a, 1508b, and 1508c, the PA IMS/SIP mobile client, located in the user's home network, includes the newly associated device information in the SIP RE-INVITE message it sends to Handoff Control Application Server (AS) module 614 (within serving node 408). In this message, the mobile station (MS) or UE includes its original SIP user identifier into the from-field of the SIP header. It also includes its new IP address into both the Contact field of the SIP header, in order to inform the corresponding host where it wants to receive future SIP messages, and also into the c (Connection) field of the SDP header that contains a description of the session, in order to redirect the data traffic flow towards its new location.
As depicted by 1509 in FIG. 15, the information about the newly discovered device is added to the ME framework database entry associated with the mobile device. In addition, as depicted by 10 in FIG. 15, the new device discovery/association event may trigger a handoff control decision to be executed in the Handoff Control Application Server module 614. This decision is driven by policy logic in policy database 902 (see FIG. 9). The policy logic includes rules that depend on technical specifications of the discovered device that determine whether the discovered device, if associated with the ongoing IMS session, would add value to the user. The policy logic may also include business-based rules that reflect the relationship of the user to the owner/operator of a discovered device.
As depicted by 1511a, 1511b, and 1511c in FIG. 15, if a handoff event is triggered, the response from the serving node towards the PA mobile client includes the handoff control information.
As depicted by 1512 and 1513 in FIG. 15, the PA IMS/SIP mobile client issues a SOAP remote procedure call to the media renderer (i.e., the device that renders the media) to initiate a RTSP streaming session. Services (i.e., media renderer) keep state tables updated so that control points can obtain meaningful values. When state variables change, events are broadcast over the home IP network to all interested control points, which may include multiple handsets having PAs and CPPs in a home environment.
As depicted by 1514 and 1515 in FIG. 15, the media renderer initiates the RTSP signaling transactions to establish a streaming session with the media server. As depicted by 1516 in FIG. 15, the PA mobile client sends a SOAP remote procedure call to the media renderer to PLAY the multimedia stream.
As depicted by 1517 in FIG. 15, the media renderer sends the RTSP Play command to the streaming media server to start the media stream. This stream is out-of-band transport of the media stream from the media server to the media renderer.
As depicted by 1518a, 1158b, and 1518c in FIG. 15, the user may optionally decide to disengage the serving node from controlling the media server and allow the media control to be handled directly from the media renderer. In this case, the PA mobile client sends a SIP RE-INVITE message towards the media server control application in the serving node to disengage.
Associated Device Discovery and Relay Session Via UPnP
The following case illustrates a session that involves the PA client discovering an associated device via UPnP discovery mechanisms, and the serving node triggering a relay procedure to allow RTSP streaming content to be relayed from the PA client to the associated device. In this case, the media transport takes place over the 2G/3G network to the handset, and from the handset it is relayed to a discovered associated device using a WLAN/PAN.
In this example, the PA acts as a SIP UE and an IMS/SIP session has been established between the PA and the Media Server Control AS in the serving node.
As depicted by 1601 to 1609 in FIG. 16, the steps involving discovery are as described above in connection with FIG. 15.
As depicted by 1610 in FIG. 16, the new device discovery/association event triggers an action to have the PA relay the content to the newly associated device.
As depicted by 1611a, 1611b, and 1611c in FIG. 16, the response from the serving node towards the PA client includes the relay control information.
As depicted by 1612 and 1613 in FIG. 16, the PA client issues a SOAP remote procedure call to the associated device, which, in this case, is a media renderer, to establish a UPnP LAN connection.
As depicted by 1614 and 1615 in FIG. 16, the PA client, serving as an UPnP media server device initiates the RTSP signaling transactions to establish a streaming session.
As depicted by 1616 in FIG. 16, the associated device operating as an UPnP media renderer sends a SOAP remote procedure call to the PA client to initiate the PLAY action to start the multimedia stream.
As depicted by 1617 in FIG. 16, the PA client sends the RTSP PLAY command to the multimedia server to start the media stream.
As depicted by 1618a, 1618b, and 1618c in FIG. 16, the user may optionally decide to disengage the serving node from controlling the media server and allow the media control to be handled directly from the media renderer. In this case, the PA client sends a SIP RE-INVITE message towards the media server control application in the ASN to disengage.
Dynamic Media Resource Control
This case illustrates a session that involves the PA client discovering an associated device via UPnP Discovery mechanisms, and the serving node triggering a handoff procedure to allow RTSP streaming content to be relayed from the PA client to the associated device. In addition, the serving node also determines that the content to be delivered to the newly associated device via the PA (relay) requires trans-coding and directs a Media Resource Control Function (MRCF) to establish the trans-coding session. Transcoding can involve, for example, changing the spatial or and/or color resolution of a video stream to take advantage of higher resolution viewing capability on a discovered device.
As described in detail below, in this case the MRCF responds to the INVITE request with a 200 OK message indicating the selected media in the SDP. The MRCF will also reserve the requested local resources at that time and return the appropriate resource identifiers in the 200 response.
In one embodiment, the Media Server Control AS controls a trans-coding session and is aware of MRCF capabilities. The MRCF accepts INVITE requests sent from the AS, via the S-CSCF, to dynamically set up the trans-coding configuration. The INVITE sent to the MRCF contains sufficient information to support the RTSP session that requires trans-coding. The MRCF always grants the requests from the AS, unless it has reached its resource limits.
It is assumed that the PA is acting as a SIP UE and that an IMS/SIP session has been established between the PA and the Media Server Control AS in the serving node.
FIG. 17 illustrates the steps involved in setting up the MRCF to provide trans-coding for a mobile originated session, where the MRCF is receiving directions from the AS operating as a back-to-back user agent (B2BUA). In other words, the AS can initiate calls/sessions itself. In FIG. 17, the number enclosed within the square brackets, i.e., the “[x]” notation, is an indicator of a particular SIP dialog.
As depicted by 1701 in FIG. 17, the media renderer device is discovered by the PA, as described in detail above.
After the Handoff Control AS has triggered a PA relay action, an RTSP streaming session is initiated from the mobile handset (1702-1719). The Media Server Control AS is aware of the different codec requirements between the PA client in the mobile handset and the newly associated device by retrieving the ME framework parameters reported by the PA when the newly terminal device is discovered and associated.
The Media Server Control AS serves as a B2BUA and interacts with the originating UE as usual to establish the dialog. The Media Server Control AS interacts with the MRCF using a third party control model, as defined in IETF RFC 3264.
The Media Server Control AS requests trans-coding facilities from the MRCF (1720). The request includes the appropriate trans-coding requirements and resources to be established. A separate dialog is established from the Media Server Control AS to the MRCF for the PA client.
The offer/answer model is used for SDP negotiation between the Media Server Control AS/S-CSCF and the MRCF.
The MRCF should always grant the requests from the AS (unless there is a resource problem). The MRCF responds to the INVITE request (1721, 1722) with a 200 response indicating the selected codec in the SDP (1723, 1724). The MRCF will also reserve the requested local resources at that time.
The media from the PA UE is connected at the trans-coding resource at the Media Resource Function Processor (MRFP).
The selected codec is included by the Media Server Control AS in the 183 response to the UE. (not on Fig.)
The receipt of the ACK at the MRCF (1725, 1726) triggers the start of the trans-coding session (1727-1730).
It will be further appreciated that the scope of the present invention is not limited to the above-described embodiments but rather is defined by the appended claims, and that these claims will encompass modifications and improvements to what has been described.

Claims (33)

What is claimed:
1. A method of controlling and delivering media content from a media server (MS) to a media renderer (MR) utilizing a wide area network for control, comprising the acts of:
provisioning a serving node in the wide area network with control point (CP) logic that includes logic to negotiate media content delivery with at least one of the MS and the MR, wherein the CP logic, MS, and MR resides outside of a user endpoint (UE) and the CP logic resides in the signaling domain and serves as a first proxy;
provisioning the UE of the wide area network with control point proxy (CPP) logic that includes (i) logic to negotiate media content delivery with at least one of the MS and the MR, (ii) logic to cooperate with CP logic to negotiate media content delivery between the MS and the MR, and (iii) video cassette recorder (VCR) controls to control a presentation of content provided by the MS and rendered by the MR, wherein the CPP logic resides in the UE and serves as a second proxy;
in response to a media content delivery request, determining a network context of the UE and a network connectivity of the MS and MR;
invoking the CPP logic and the CP logic to cooperatively negotiate media content delivery between the MS and the MR if one of the MS and MR are not in communication with the UE via a local wireless network; and
once media content delivery is negotiated, controlling a presentation of delivery via the VCR controls on the UE.
2. The method of claim 1, wherein the CPP logic is invoked to negotiate media content delivery between the MS and the MR if the MS and MR are both in communication with the UE via a local wireless network.
3. The method of claim 2, wherein the local wireless network includes at least one a Wi-Fi network, a WiMax network, and a Bluetooth network.
4. The method of claim 1, wherein the CP logic is invoked to negotiate media content delivery between the MS and the MR if neither the MS nor the MR are in communication with the UE via the local wireless network.
5. The method of claim 1, wherein the UE is implemented on a handset.
6. The method of claim 5, wherein the handset comprises a display, and the MR uses the display.
7. The method of claim 1, wherein at least one of the MS and the MR is on a 3G network and in communication with the serving node.
8. The method of claim 1, wherein the UE is in communication with the MR via a local wireless network.
9. The method of claim 1, wherein the UE is in communication with both the MS and the MR via a local wireless network.
10. The method of claim 1, wherein the CP logic negotiates service delivery from the MS, the MS being on a 3G network, the CPP logic in the UE negotiates delivery on the MR, and the CP logic and CPP logic execute synchronization logic to complete the negotiation of delivery from the MS to the MR.
11. The method of claim 1, wherein the UE communicates its network context to the serving node and the serving node informs the UE of the serving node's capabilities for negotiation with devices local to the UE.
12. The method of claim 1, wherein the CP logic is configured to serve multiple unrelated devices running CPP logic.
13. The method of claim 12, wherein CPP logic is implemented in a UE resident in a handset and in a remote control device.
14. The method of claim 13, wherein a user uses the CPP logic in the handset when the user is remote from the MR and uses the CPP logic in the remote control device when the user is local to the MR.
15. The method of claim 1, wherein, if one of the MS and MR are remote from the UE, the CPP logic provides information about invoked VCR controls to the CP logic on the serving node to allow the CP logic to control the remote MS or MR.
16. The method of claim 1, wherein the MS and the MR are in a digital home network.
17. The method of claim 1, wherein the UE determines that it is local to at least one of the MS and the MR by using Universal Plug and Play (UPnP) protocols.
18. The method of claim 1, wherein at least one of the MS and MR announce their presence to the UE using at least one of UPnP protocols, Jini technology, RFID, and Bluetooth.
19. The method of claim 1, wherein the negotiation of media content delivery includes the negotiation of out-of-band media transfer between the MS and the MR.
20. A method of controlling and delivering media content from a media server (MS) to a media renderer (MR) utilizing a wide area network for control, where a user endpoint (UE) is provisioned with control point proxy (CPP) logic that includes (i) logic to negotiate media content delivery with at least one of the MS and the MR, (ii) logic to cooperate with network control point (CP) logic to negotiate media content delivery between the MS and the MR, and (iii) video play controls to control a presentation of content provided by the MS and rendered by the MR, wherein the CPP logic resides in the UE and serves as a first proxy, comprising the acts of:
provisioning a serving node in the wide area network with control point (CP) logic that includes logic to negotiate media content delivery with at least one of the MS and the MR, wherein the CP logic, MS, and MR resides outside of a user endpoint (UE) and the CP logic resides in the signaling domain and serves as a second proxy;
in response to a media content delivery request, the wide area network determining a network context of the UE and a network connectivity of the MS and MR;
invoking the CPP logic and the CP logic to cooperatively negotiate media content delivery between the MS and the MR if one of the MS and MR are not in communication with the UE via a local wireless network; and
once media content delivery is negotiated, receiving video play controls from the UE.
21. The method of claim 20, wherein the CPP logic is invoked to negotiate media content delivery between the MS and the MR if the MS and MR are both in communication with the UE via a local wireless network.
22. The method of claim 21, wherein the local wireless network includes at least one a wi-fi network, a wimax network, and a Bluetooth network.
23. The method of claim 20, wherein the CP logic is invoked to negotiate media content delivery between the MS and the MR if neither the MS nor the MR are in communication with the UE via the local wireless network.
24. The method of claim 20, wherein the MS and the MR are in a digital home network.
25. The method of claim 20, wherein at least one of the MS and MR announce their presence to the UE using at least one of UPnP protocols, Jini technology, RFID, and Bluetooth.
26. The method of claim 20, wherein the negotiation of media content delivery includes the negotiation of out-of-band media transfer between the MS and the MR.
27. A user endpoint (UE) for communication with a serving node in a network, the serving node having control point (CP) logic that includes logic to negotiate media content delivery with at least one of a media server (MS) and a media renderer (MR), wherein the CP logic, MS, and MR reside outside of the UE and the CP logic resides in the signaling domain and serves as a first proxy, the UE comprising:
a transceiver to communicate with the network, the MS and the MR; and
a computer readable medium comprising:
personal agent logic configured to determine a network context of the UE; and
control point proxy logic configured to:
negotiate media content delivery with at least one of the MS and the MR,
cooperate with the serving node CP logic to negotiate media content delivery between the MS and the MR, and
once media content delivery is negotiated, control a presentation of media content provided by the MS and rendered by the MR with video play controls.
28. The UE of claim 27 comprising a display, and the MR uses the display.
29. The UE of claim 27, wherein the UE is in communication with one or more of the MS and the MR via a local wireless network.
30. The UE of claim 29, wherein the local wireless network includes at least one a wi-fi network, a wimax network, and a Bluetooth network.
31. The UE of claim 27, wherein the UE determines that it is local to at least one of the MS and the MR by using universal plug and play (UPnP) protocols.
32. The UE of claim 27, wherein the UE communicates its network context to the serving node and receives from the serving node the serving node's capabilities for negotiation with devices local to the UE.
33. The UE of claim 27, wherein the UE is implemented on a handset.
US13/232,432 2005-06-24 2011-09-14 Digital home networks having a control point located on a wide area network Expired - Fee Related USRE44412E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/232,432 USRE44412E1 (en) 2005-06-24 2011-09-14 Digital home networks having a control point located on a wide area network

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/166,407 US7792528B2 (en) 2005-06-24 2005-06-24 Method and system for provisioning IMS networks with virtual service organizations having distinct service logic
US11/282,924 US20060291487A1 (en) 2005-06-24 2005-11-18 IMS networks with AVS sessions with multiple access networks
US11/370,793 US7724753B2 (en) 2005-06-24 2006-03-08 Digital home networks having a control point located on a wide area network
US13/232,432 USRE44412E1 (en) 2005-06-24 2011-09-14 Digital home networks having a control point located on a wide area network

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/370,793 Reissue US7724753B2 (en) 2005-06-24 2006-03-08 Digital home networks having a control point located on a wide area network

Publications (1)

Publication Number Publication Date
USRE44412E1 true USRE44412E1 (en) 2013-08-06

Family

ID=46324021

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/370,793 Ceased US7724753B2 (en) 2005-06-24 2006-03-08 Digital home networks having a control point located on a wide area network
US13/232,432 Expired - Fee Related USRE44412E1 (en) 2005-06-24 2011-09-14 Digital home networks having a control point located on a wide area network

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/370,793 Ceased US7724753B2 (en) 2005-06-24 2006-03-08 Digital home networks having a control point located on a wide area network

Country Status (1)

Country Link
US (2) US7724753B2 (en)

Cited By (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215815A1 (en) * 2009-01-28 2015-07-30 Headwater Partners I Llc Device-Assisted Services for Protecting Network Capacity
US9198117B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Network system with common secure wireless message service serving multiple applications on multiple wireless devices
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9204282B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9215159B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Data usage monitoring for media data services used by applications
US9225797B2 (en) 2009-01-28 2015-12-29 Headwater Partners I Llc System for providing an adaptive wireless ambient service to a mobile device
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9386165B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc System and method for providing user notifications
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9491199B2 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9532261B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc System and method for wireless network offloading
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565543B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Device group partitions and settlement platform
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9591474B2 (en) 2009-01-28 2017-03-07 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US20170094551A1 (en) * 2015-09-30 2017-03-30 Intel IP Corporation Interference mitigation by a scalable digital wireless modem
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9769207B2 (en) 2009-01-28 2017-09-19 Headwater Research Llc Wireless network service interfaces
US9819808B2 (en) 2009-01-28 2017-11-14 Headwater Research Llc Hierarchical service policies for creating service usage data records for a wireless end-user device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10070305B2 (en) 2009-01-28 2018-09-04 Headwater Research Llc Device assisted services install
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10320763B2 (en) * 2013-06-25 2019-06-11 Google Inc. Efficient communication for devices of a home network
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10681100B2 (en) * 2007-08-17 2020-06-09 Huawei Technologies Co., Ltd. Method, user equipment and application server for adding media stream of multimedia session
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11973804B2 (en) 2009-01-28 2024-04-30 Headwater Research Llc Network service plan design
US11985155B2 (en) 2009-01-28 2024-05-14 Headwater Research Llc Communications device with secure data path processing agents

Families Citing this family (78)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60023359T2 (en) * 2000-08-10 2006-07-06 Nokia Corp. Method and system for roaming support in UMTS
US7310696B1 (en) * 2004-12-03 2007-12-18 Crossroads Systems, Inc. Method and system for coordinating interoperability between devices of varying capabilities in a network
US7672297B2 (en) * 2005-06-24 2010-03-02 Aylus Networks, Inc. Mediation system and method for hybrid network including an IMS network
US7561535B2 (en) * 2005-06-24 2009-07-14 Aylus Networks, Inc. System and method for providing dynamic call models for users as function of the user environment in an IMS network
US20060291412A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A Associated device discovery in IMS networks
US7792528B2 (en) 2005-06-24 2010-09-07 Aylus Networks, Inc. Method and system for provisioning IMS networks with virtual service organizations having distinct service logic
US7864936B2 (en) 2005-06-24 2011-01-04 Aylus Networks, Inc. Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
KR100739794B1 (en) * 2006-02-13 2007-07-13 삼성전자주식회사 Method and apparatus for providing broadcast content in upnp network
US7979031B2 (en) * 2006-03-14 2011-07-12 Agilent Technologies, Inc. System and method for making measurements in customer devices across different network technologies
CN101047705B (en) * 2006-03-31 2013-01-30 华为技术有限公司 Report process method, server for customer agent file information and its customer terminal
US8432899B2 (en) 2007-02-22 2013-04-30 Aylus Networks, Inc. Systems and methods for enabling IP signaling in wireless networks
US8730945B2 (en) 2006-05-16 2014-05-20 Aylus Networks, Inc. Systems and methods for using a recipient handset as a remote screen
US8611334B2 (en) 2006-05-16 2013-12-17 Aylus Networks, Inc. Systems and methods for presenting multimedia objects in conjunction with voice calls from a circuit-switched network
US9026117B2 (en) 2006-05-16 2015-05-05 Aylus Networks, Inc. Systems and methods for real-time cellular-to-internet video transfer
US20070280453A1 (en) * 2006-05-30 2007-12-06 Motorola, Inc. Method and system to provide access network information to a service
US8166176B2 (en) * 2006-05-31 2012-04-24 Alcatel Lucent Context-aware migration of communication session
US20070286100A1 (en) * 2006-06-09 2007-12-13 Mika Juhani Saaranen Local discovery of mobile network services
ITTO20060500A1 (en) * 2006-07-06 2008-01-07 St Microelectronics Srl SYSTEM FOR THE DISTRIBUTED PROCESSING OF MULTIMEDIA CONTENT IN COMMUNICATION NETWORKS, IN PARTICULAR OF A DOMESTIC TYPE, RELATED PROCEDURE AND IT PRODUCT
DE602006017839D1 (en) * 2006-08-23 2010-12-09 Alcatel Lucent Method for registering a plurality of permanently registered subscribers in an IMS subsystem of an NGN system
US8255549B2 (en) * 2006-10-09 2012-08-28 At&T Intellectual Property I, Lp Method and apparatus for delivering IP multimedia subsystem services
US9008081B2 (en) * 2006-12-14 2015-04-14 Rpx Clearinghouse Llc Serving gateway proxies for non-SIP speakers in a next generation network
US8384753B1 (en) 2006-12-15 2013-02-26 At&T Intellectual Property I, L. P. Managing multiple data sources
US9531835B2 (en) * 2007-02-13 2016-12-27 Devicescape Software, Inc. System and method for enabling wireless social networking
US20080207177A1 (en) * 2007-02-23 2008-08-28 Kunal Shukla Method and apparatus providing voice mail service for half duplex wireless communication systems
US7856226B2 (en) 2007-04-17 2010-12-21 Aylus Networks, Inc. Systems and methods for IMS user sessions with dynamic service selection
EP2137632A4 (en) 2007-04-17 2014-11-26 Aylus Networks Inc Systems and methods for using a recipient handset as a remote screen
CN101304350B (en) * 2007-05-11 2013-02-13 华为技术有限公司 Method and system for accessing household network equipment as well as household network access equipment
US8943190B1 (en) * 2007-07-20 2015-01-27 Avaya Inc. Call-processing event-notification server
US20090093247A1 (en) * 2007-10-03 2009-04-09 Microsoft Corporation WWAN device provisioning using signaling channel
US20090093248A1 (en) * 2007-10-03 2009-04-09 Microsoft Corporation WWAN device provisioning using signaling channel
US8949434B2 (en) * 2007-12-17 2015-02-03 Microsoft Corporation Automatically provisioning a WWAN device
US20090180398A1 (en) * 2008-01-16 2009-07-16 Sony Corporation, A Japanese Corporation Method and apparatus for facilitating interaction between the services provided by respective networked devices
US8948752B2 (en) * 2008-01-24 2015-02-03 At&T Intellectual Property I, L.P. System and method of providing IMS services to users on originating non IMS devices and other devices that do not have a previous relationship with the user
US9246950B2 (en) * 2008-01-24 2016-01-26 At&T Intellectual Property I, L.P. System and method of providing registration macros in an IMS network-based device
US9241253B2 (en) 2008-01-24 2016-01-19 At&T Intellectual Property I, L.P. System and method of providing a user with a registration review in IMS system
US9246951B2 (en) * 2008-01-24 2016-01-26 At&T Intellectual Property I, L.P. System and method of remotely de-registering devices in IMS system
US8972374B2 (en) * 2008-02-12 2015-03-03 International Business Machines Corporation Content acquisition system and method of implementation
US8788888B2 (en) * 2008-03-14 2014-07-22 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for providing end user notification in a UPnP network
WO2009135301A1 (en) 2008-05-07 2009-11-12 Chalk Media Service Corp. Method for enabling bandwidth management for mobile content delivery
CN101989980A (en) * 2009-08-04 2011-03-23 鸿富锦精密工业(深圳)有限公司 Multimedia sharing method
US9124597B2 (en) * 2009-09-17 2015-09-01 Telefonaktiebolaget Lm Ericsson (Publ) Method and node in a telecommunications network
US9781197B2 (en) * 2009-11-30 2017-10-03 Samsung Electronics Co., Ltd. Methods and apparatus for selection of content delivery network (CDN) based on user location
US8451841B2 (en) 2009-12-28 2013-05-28 At&T Intellectual Property I, L.P. Method and apparatus for processing a call to an aggregate endpoint device
US8793388B2 (en) * 2009-12-28 2014-07-29 At&T Intellectual Property I, L.P. Method and apparatus for processing a call to an aggregate endpoint device
WO2011096691A2 (en) 2010-02-03 2011-08-11 Samsung Electronics Co., Ltd. System and method for file transfer in universal plug and play telephony service
US9471700B2 (en) 2010-05-18 2016-10-18 Tksn Holdings, Llc System and method for monitoring changes in databases and websites
US20120021770A1 (en) 2010-07-21 2012-01-26 Naqvi Shamim A System and method for control and management of resources for consumers of information
US9210528B2 (en) 2010-07-21 2015-12-08 Tksn Holdings, Llc System and method for control and management of resources for consumers of information
US9232046B2 (en) 2010-07-21 2016-01-05 Tksn Holdings, Llc System and method for controlling mobile services using sensor information
US9241190B2 (en) * 2010-08-24 2016-01-19 Cisco Technology, Inc. Generating a response to video content request including dynamically processed video content
US8068011B1 (en) 2010-08-27 2011-11-29 Q Street, LLC System and method for interactive user-directed interfacing between handheld devices and RFID media
CN102420802A (en) * 2010-09-27 2012-04-18 中兴通讯股份有限公司 Method and system for accessing circuit switch domain call through visited IMS (IP Multimedia System) access point
KR20120072115A (en) 2010-12-23 2012-07-03 삼성전자주식회사 Apparatus and method for expanding upnp network area
WO2012125094A1 (en) * 2011-03-11 2012-09-20 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses in communication systems
US9762662B2 (en) * 2011-05-12 2017-09-12 Microsoft Technology Licensing, Llc Mass re-formation of groups in a peer-to-peer network
US9872080B2 (en) * 2011-08-26 2018-01-16 Samsung Electronics Co., Ltd. Home network media transport negotiation
TWI475877B (en) * 2011-08-30 2015-03-01 Wistron Corp Display apparatus and video displaying method
JP2013074498A (en) * 2011-09-28 2013-04-22 Sanyo Electric Co Ltd Television receiver, portable information terminal, and information exchange system including them
US9521439B1 (en) 2011-10-04 2016-12-13 Cisco Technology, Inc. Systems and methods for correlating multiple TCP sessions for a video transfer
US8755342B2 (en) 2011-10-05 2014-06-17 Cisco Technology, Inc. System and method for dynamic bearer selection for immersive video collaboration in mobile wireless networks
US8903955B2 (en) 2011-12-02 2014-12-02 Cisco Technology, Inc. Systems and methods for intelligent video delivery and cache management
US10764429B2 (en) * 2012-01-16 2020-09-01 Lakshman R. Bana System and method for displaying content on a mobile communications device
US8819841B2 (en) * 2012-06-26 2014-08-26 Google Inc. Automated accounts for media playback
US9749373B2 (en) * 2012-08-14 2017-08-29 Apple Inc. System and method for improved content streaming
GB2505476B (en) * 2012-08-31 2019-02-27 Metaswitch Networks Ltd Processing communication sessions
US9565475B2 (en) 2012-10-11 2017-02-07 Netflix, Inc. System and method for managing playback of streaming digital content
US9727321B2 (en) 2012-10-11 2017-08-08 Netflix, Inc. System and method for managing playback of streaming digital content
KR102097640B1 (en) * 2013-03-08 2020-04-06 엘지전자 주식회사 Mobile terminal and control method thereof
US10097694B1 (en) * 2013-09-27 2018-10-09 Google Llc Method and system for moving phone call participation between carrier and data networks
US9986044B2 (en) * 2013-10-21 2018-05-29 Huawei Technologies Co., Ltd. Multi-screen interaction method, devices, and system
WO2015182976A1 (en) 2014-05-28 2015-12-03 Samsung Electronics Co., Ltd. Mobile apparatus, display apparatus, and multimedia output method using the same
US10390289B2 (en) 2014-07-11 2019-08-20 Sensoriant, Inc. Systems and methods for mediating representations allowing control of devices located in an environment having broadcasting devices
US9552587B2 (en) 2014-07-11 2017-01-24 Sensoriant, Inc. System and method for mediating representations with respect to preferences of a party not located in the environment
US10701165B2 (en) 2015-09-23 2020-06-30 Sensoriant, Inc. Method and system for using device states and user preferences to create user-friendly environments
US9848214B2 (en) 2015-10-01 2017-12-19 Sorenson Media, Inc. Sequentially overlaying media content
US9723347B2 (en) 2015-10-01 2017-08-01 Sorenson Media, Inc Frequency capping for media content
US10609185B2 (en) * 2015-11-04 2020-03-31 Rockwell Automation Technologies, Inc. Method for topology tree to learn about, present, and configure device information by automatically uploading device description files from device
US11483684B1 (en) * 2021-05-07 2022-10-25 T-Mobile Usa, Inc. Session recovery from dedicated bearer failure

Citations (139)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4736407A (en) 1986-04-08 1988-04-05 The United States Of America As Represented By The Secretary Of The Army Computer assisted graphic teleconferencing method and apparatus
US4925311A (en) 1986-02-10 1990-05-15 Teradata Corporation Dynamically partitionable parallel processors
US6014706A (en) * 1997-01-30 2000-01-11 Microsoft Corporation Methods and apparatus for implementing control functions in a streamed video display system
US6018662A (en) 1998-09-08 2000-01-25 Nortel Networks Corporation Method for performing progressive soft handoff in CDMA systems
US6032053A (en) 1995-07-19 2000-02-29 Pacific Communications Science, Inc. Signaling the type of incoming telephone calls
US6047194A (en) 1997-09-23 2000-04-04 Telefonaktiebolaget L M Ericsson (Publ) Method, and associated apparatus, for selectively permitting transmission of packet data to a mobile terminal
US6061572A (en) 1997-12-15 2000-05-09 Telefonaktiebolaget L M Ericsson (Publ) Digital cellular telecommunications with short message service over the packet channel
US6067529A (en) 1998-08-12 2000-05-23 Ericsson Inc. System and method for sending a short message containing purchase information to a destination terminal
US6374112B1 (en) 1998-04-03 2002-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Flexible radio access and resource allocation in a universal mobile telephone system
US20020059416A1 (en) 1999-07-09 2002-05-16 Heikki Tuunanen Management of performance of intelligent network services
US20020064274A1 (en) 1999-06-14 2002-05-30 Heikki Tuunanen Initiating a controlling service
US20020140726A1 (en) 2000-12-22 2002-10-03 Schwartz Richard L. Method and system for facilitating mediated communication
US20020181462A1 (en) 2001-04-24 2002-12-05 Sorin Surdila System and method for providing end-to-end quality of service (QoS) across multiple internet protocol (IP) networks
US20030027595A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Provision of services in a communication system including an interworking mobile switching center
US20030026245A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system including an interworking mobile switching center for call termination
US20030027569A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system for providing roaming between an internet protocol multimedia system and a circuit-switched domain
US20030055974A1 (en) 1999-08-24 2003-03-20 Kevin Brophy Systems and methods for providing unified multimedia communication services
US6574326B1 (en) 1999-11-18 2003-06-03 Nokia Network Oy Method and system for minimizing transmission of optional parameters in an intelligent network environment
US20030134636A1 (en) * 2002-01-02 2003-07-17 Rangamani Sundar Method, system, and apparatus for a mobile station to sense and select a wireless local area network (WLAN) or a wide area mobile wireless network (WWAN)
US20030134640A1 (en) 2001-12-29 2003-07-17 Samsung Electronics Co., Ltd Apparatus and method for initiating a broadcast service by a mobile station in a mobile communication system
US20030144008A1 (en) 2002-01-28 2003-07-31 Rehkopf Thomas W. System and method for accessing computer services via a wireless network
US6608832B2 (en) 1997-09-25 2003-08-19 Telefonaktiebolaget Lm Ericsson Common access between a mobile communications network and an external network with selectable packet-switched and circuit-switched and circuit-switched services
US20030193426A1 (en) * 2002-04-12 2003-10-16 Alberto Vidal Apparatus and method to facilitate universal remote control
US20030210683A1 (en) 2002-05-07 2003-11-13 Koninklijke Kpn N.V. Telecommunication system
US6650705B1 (en) 2000-05-26 2003-11-18 Mitsubishi Electric Research Laboratories Inc. Method for encoding and transcoding multiple video objects with variable temporal resolution
US6665711B1 (en) 1998-04-30 2003-12-16 Openwave Systems Inc. Method and apparatus for integrating narrowband and wideband data transports
US6675196B1 (en) 1999-01-08 2004-01-06 Amazon.Com, Inc. Universal protocol for enabling a device to discover and utilize the services of another device
US20040008669A1 (en) 2002-06-03 2004-01-15 Alcatel Telecommunication system with packet-switched-multimedia-session-to-circuit-switched-call transferral
US20040019539A1 (en) 2002-07-25 2004-01-29 3Com Corporation Prepaid billing system for wireless data networks
US20040019901A1 (en) 2002-04-29 2004-01-29 The Boeing Company Methodology for display/distribution of multiple content versions based on demographics
US6694145B2 (en) 2001-12-27 2004-02-17 Nokia Corporation Synchronization of signaling messages and multimedia content loading
US20040043766A1 (en) 2002-08-27 2004-03-04 Nec Corporation System and method for informing that user is in or not in wireless LAN service
US20040048612A1 (en) 2002-09-09 2004-03-11 Kejio Virtanen Unbroken primary connection switching between communications services
US20040062230A1 (en) 2002-10-01 2004-04-01 Nortel Networks Limited Integrating multimedia capabilities with legacy networks
US20040068574A1 (en) 2002-10-03 2004-04-08 Nokia Corporation WV-IMS relay and interoperability methods
US20040076145A1 (en) 2000-12-22 2004-04-22 Timo Kauhanen Method and system for establishing a multimedia connection by negotiating capability in an outband control channel
US20040083195A1 (en) 2002-10-23 2004-04-29 Mccord Alan Wayne Method and system for enabling automated and real-time discovery of skills available to agents and systems in a multimedia communications network
US20040107143A1 (en) * 2002-11-29 2004-06-03 Aki Niemi Method for authorizing indirect content download
US20040127251A1 (en) 2002-12-16 2004-07-01 Thakkar Vivek V. Method and apparatus for mixed mode personal communication
US20040162892A1 (en) 2003-02-18 2004-08-19 Hsu Raymond T. Provisioning server information in a mobile station
US20040193700A1 (en) 2003-03-25 2004-09-30 Ilkka Westman Service provisioning in a communication system
US20040193725A1 (en) 2003-03-25 2004-09-30 Jose Costa-Requena Optimal location service for managing next hop addressing for messages associated with multiple address schemes
US20040205212A1 (en) 2003-03-31 2004-10-14 Nokia Corporation Method and system for forwarding a service-related information to a network user
US20040219912A1 (en) 2003-04-29 2004-11-04 Klas Johansson Method and system for exchanging the capacity reports in a radio access network
US20040218571A1 (en) 2000-07-12 2004-11-04 Michael Pascazi System and method for cellphone to cell phone signal transmission via the internet
US20040249962A1 (en) 2001-11-28 2004-12-09 Medialive, A Corporation Of France Method and system for accessing video and multimedia electronic mail
US20040249887A1 (en) 2003-02-15 2004-12-09 Miguel-Angel Garcia-Martin Conversational bearer negotiation
US20040252673A1 (en) 2003-06-11 2004-12-16 Ejzak Richard Paul Server component redirection of new media path portion between packet-switched and circuit-switched portions of mobile switching center
US20040261116A1 (en) 2001-07-03 2004-12-23 Mckeown Jean Christophe Broadband communications
US6847632B1 (en) 1998-12-22 2005-01-25 Nortel Networks Limited Method and apparatus for digital cellular internet voice communications
US20050021494A1 (en) 2001-10-19 2005-01-27 Nokia Inc. Selective media capture via a communication device
US20050025163A1 (en) 2003-07-28 2005-02-03 Nortel Networks Limited Mobility in a multi-access communication network
US6857021B1 (en) 1998-10-30 2005-02-15 3Com Corporation Proximity-based registration on a data network telephony system
US20050043020A1 (en) 2001-11-20 2005-02-24 Matti Lipsanen Mobile telecommunication networks and digital broadcasting services
US20050047399A1 (en) 2003-08-29 2005-03-03 Sang-Do Lee Method and apparatus for providing voice and data services in a mobile communication system with various overlapped access networks
US20050050194A1 (en) 2002-01-10 2005-03-03 Bernhard Honeisen Method and system for proxying a message
US20050058125A1 (en) 2003-09-11 2005-03-17 Nokia Corporation IP-based services for circuit-switched networks
US20050063329A1 (en) 2003-09-19 2005-03-24 Sang-Do Lee Data push service system and method using a heterogeneous network
US20050083909A1 (en) 2003-10-17 2005-04-21 Jarmo Kuusinen System, apparatus, and method for establishing circuit-switched communications via packet-switched network signaling
US20050089020A1 (en) 2002-03-27 2005-04-28 Telefonaktiebolaget Lm Erisson (Publ) Charging in a communications network
US6888828B1 (en) 2001-10-02 2005-05-03 Nokia Corporation System and method for providing at least one service obtained from a service network for a user in a packet switched communication network
US20050114493A1 (en) * 2003-10-22 2005-05-26 Davide Mandato Context-aware automatic service discovery and execution engine in mobile ad-hoc networks
EP1545129A1 (en) 2003-12-16 2005-06-22 Hutchison Whampoa Three G IP (Bahamas) Limited Push to watch : a video person-to-person streaming application
US20050180394A1 (en) 2004-02-13 2005-08-18 Olaf Kautz Method for changing between a packet-oriented PTT session and a circuit-oriented telephone connection between at least two radio communication appliances, associated radio communication appliance, network component and radio communication system
US20050190772A1 (en) 2004-02-26 2005-09-01 Shang-Chih Tsai Method of triggering application service using filter criteria and IP multimedia subsystem using the same
US6950655B2 (en) 2002-10-01 2005-09-27 Interdigital Technology Corporation Method and system wherein handover information is broadcast in wireless local area networks
US20050213606A1 (en) 2004-03-25 2005-09-29 Jiun-Yao Huang Method of triggering application service using response filter criteria and IP multimedia subsystem using the same
US20050227681A1 (en) 2004-04-08 2005-10-13 Shenzhen Dianjing Technology Co. Ltd. Method and communication system of associated phone calling
US20050237933A1 (en) 2004-03-30 2005-10-27 Pekka Marjelund Delivering services in a wireless communications system
US20050243870A1 (en) 2004-04-14 2005-11-03 Balogh Dan A Method of transferring call transition messages between network controllers of different radio technologies
US20050245261A1 (en) * 2004-04-14 2005-11-03 Ejzak Richard P Method of handing off a packet switched to a circuit switched call
US20050271011A1 (en) 2004-06-07 2005-12-08 Nokia Inc. Vertical network handovers
US20050286531A1 (en) 2002-07-16 2005-12-29 Markku Tuohino Optimized routing between communication networks
US20060015812A1 (en) 2004-07-15 2006-01-19 Cingular Wireless Ii, Llc Using emoticons, such as for wireless devices
US20060025151A1 (en) 2004-07-28 2006-02-02 Jeyhan Karaoguz Handoff of a multimedia call session using background network scanning
EP1435748B1 (en) 2002-12-30 2006-03-29 France Telecom Handover between wireless networks of different technologies
US7024198B2 (en) 2001-08-23 2006-04-04 Siemens Aktiengellschaft Method for expediting a short message via a server when a communication participant of a communication network is not available
US20060080407A1 (en) * 2004-10-12 2006-04-13 Motorola, Inc. Multimedia session establishment in a user entity having audio floor control
US20060083199A1 (en) 2004-10-15 2006-04-20 Yang Jianhao M System, method, and device for handing off between voice over internet protocol over wireless access sessions and CDMA circuit switched voice sessions
US20060104262A1 (en) 2004-11-18 2006-05-18 Azaire Networks Inc. Maintaining consistent network connections while moving through wireless networks
US20060114987A1 (en) 1998-12-21 2006-06-01 Roman Kendyl A Handheld video transmission and display
US20060120287A1 (en) 2004-12-03 2006-06-08 George Foti Seamless handoff for multimedia services
US20060120339A1 (en) 2004-12-08 2006-06-08 Oki Electric Industry Co., Ltd. Method of controlling quality of service for a wireless LAN base station apparatus
US20060126562A1 (en) 2004-12-14 2006-06-15 Huitao Liu Method and system for seamless service availability for multi-mode terminals in different access networks
EP1672893A1 (en) 2004-12-20 2006-06-21 Star Home GmbH Apparatus and method for pre-call notification of a callee
US20060140150A1 (en) 2004-11-05 2006-06-29 Interdigital Technology Corporation Wireless communication method and system for implementing media independent handover between technologically diversified access networks
US20060149811A1 (en) * 2004-12-31 2006-07-06 Sony Ericsson Mobile Communications Ab Method for remotely controlling media devices via a communication network
US7076554B1 (en) 1999-06-11 2006-07-11 Nec Infrontia Corporation Internet service telephone communication connection method
US20060155814A1 (en) 2004-12-31 2006-07-13 Sony Ericsson Mobile Communications Ab Media client architecture for networked communication devices
US20060155850A1 (en) * 2003-11-25 2006-07-13 Matsushita Electric Industrial Co., Ltd. Networked mobile EPG service architecture
US20060164550A1 (en) 2003-04-24 2006-07-27 Kyosuke Yoshimoto Video device, video module unit, and video device operation method
US20060209768A1 (en) 2003-01-14 2006-09-21 Matsushita Electric Industrial Co., Ltd. Service in wlan inter-working, address management system, and method
US20060221903A1 (en) 2005-03-30 2006-10-05 Nokia Corporation Communication connection control mechanism in a core network ordered access change scenario
US20060246903A1 (en) 2005-04-29 2006-11-02 Samsung Electronics Co., Ltd. System and method for voice data handoff between cellular network and WiBro/WLAN network in heterogeneous network environment
US20060250578A1 (en) * 2005-05-06 2006-11-09 Pohl Garrick G Systems and methods for controlling, monitoring, and using remote applications
US20060256751A1 (en) 2005-05-11 2006-11-16 Cisco Technology, Inc. System and method for offering seamless connectivity across multiple devices in a communications environment
US20060258394A1 (en) 2005-05-11 2006-11-16 Dhillon Harry S Short message service encapsulation of supplementary service requests for IMS
US20060262806A1 (en) 2005-05-19 2006-11-23 Imed Bouazizi System and method for data delivery
US7155305B2 (en) * 2003-11-04 2006-12-26 Universal Electronics Inc. System and methods for home appliance identification and control in a networked environment
US20060291419A1 (en) 2005-06-22 2006-12-28 Sprint Spectrum L.P. Method and system for managing communication sessions during multi-mode mobile station handoff
US20060291412A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A Associated device discovery in IMS networks
US20060291487A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. IMS networks with AVS sessions with multiple access networks
US20060291488A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. System and method of interworking non-IMS and IMS networks to create new services utilizing both networks
US20060291484A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
US20060291437A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A System and method to provide dynamic call models for users in an IMS network
US20060291489A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. System and method to mediate delivery of legacy, non-IMS services into an IMS network
US20070008913A1 (en) 2005-06-24 2007-01-11 Naqvi Shamim A Method and system for provisioning IMS networks with virtual service organizations having distinct service logic
US20070008951A1 (en) 2005-06-24 2007-01-11 Naqvi Shamim A Mediation system and method for hybrid network including an IMS network
US20070014281A1 (en) 2005-06-15 2007-01-18 Azaire Networks Voice call continuity application server between IP-CAN and CS networks
WO2007010070A2 (en) 2005-07-20 2007-01-25 Createcna Xxi S.L. System for live television broadcasting from a mobile telephone
US20070033286A1 (en) 2003-09-15 2007-02-08 Ku-Bong Min Method for setting media streaming parameter of upnp-based network
US20070050510A1 (en) 2005-03-14 2007-03-01 Roamware, Inc. Session-based multimedia messaging service
US20070053343A1 (en) 2003-06-19 2007-03-08 Janne Suotula Conversational bearer negotiation
US7194235B2 (en) 2003-06-03 2007-03-20 Nokia Corporation System, method, and apparatus for facilitating media content channels
US20070066347A1 (en) 2005-09-19 2007-03-22 Silverbrook Research Pty Ltd Printing a puzzle using a mobile device
US20070067807A1 (en) 2005-09-16 2007-03-22 O'neil Douglas Methods, systems, and computer program products for providing multimedia information services over a communication network
US20070143489A1 (en) * 2005-12-20 2007-06-21 Pantalone Brett A Communication network device for universal plug and play and Internet multimedia subsystems networks
US20070143488A1 (en) * 2005-12-20 2007-06-21 Pantalone Brett A Virtual universal plug and play control point
US20070155310A1 (en) 2005-12-31 2007-07-05 Rob Borcic Interrupting and resuming a media player
US20070165599A1 (en) 2003-12-30 2007-07-19 Robert Skog Method and communication system for automatically discovering the common multimedia service capability
US20070174471A1 (en) 2003-04-30 2007-07-26 Cedric Van Rossum Secure, continous, proxy-optimized, device-to-device data download reception system and method of use
US20070197227A1 (en) 2006-02-23 2007-08-23 Aylus Networks, Inc. System and method for enabling combinational services in wireless networks by using a service delivery platform
US20070207782A1 (en) 2006-03-06 2007-09-06 Tran Bao Q Multimedia telephone
US20070217349A1 (en) 2003-12-22 2007-09-20 Gabor Fodor System and Method for Multi-Access
US7277416B1 (en) 2003-09-02 2007-10-02 Cellco Partnership Network based IP address assignment for static IP subscriber
WO2007117730A2 (en) 2006-01-13 2007-10-18 Dilithium Networks Pty Ltd. Interactive multimedia exchange architecture and services
US7301938B2 (en) 2004-04-14 2007-11-27 Lucent Technologies Inc. Method of transferring a packet switched to a circuit switched call
US20080043717A1 (en) 2003-09-19 2008-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Exchange Protocol For Combinational Multimedia Services
US20080092178A1 (en) 2006-10-11 2008-04-17 Cingular Wireless Ii, Llc Streaming video
US20080162637A1 (en) 2006-11-03 2008-07-03 At&T Bls Intellectual Property, Inc. Application services infrastructure for next generation networks including a notification capability and related methods and computer program products
US20080291905A1 (en) 2006-05-16 2008-11-27 Kiran Chakravadhanula Systems and Methods for Real-Time Cellular-to-Internet Video Transfer
US20090092109A1 (en) * 2005-12-19 2009-04-09 Torbjorn Cagenius Method and Apparatus for Enabling Discovery Within a Home Network
US7519075B2 (en) 2004-12-10 2009-04-14 Mediatek Inc. Method and system for serverless VoIP service in personal communication network
US7640038B2 (en) 2002-05-22 2009-12-29 Interdigital Technology Corporation Mobile unit having internet protocol functionality
US7637424B2 (en) 2005-09-19 2009-12-29 Silverbrook Research Pty Ltd Printing audio information using a mobile device
US7720489B2 (en) 2006-10-12 2010-05-18 At&T Mobility Ii Llc Network initiated USSD in mixed networks
US7729298B2 (en) 2004-11-08 2010-06-01 Motorola, Inc. Method and system for manipulating a shared object
US7856226B2 (en) 2007-04-17 2010-12-21 Aylus Networks, Inc. Systems and methods for IMS user sessions with dynamic service selection
US8065402B2 (en) 2004-01-20 2011-11-22 International Business Machines Corporation Network management using short message service

Patent Citations (144)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4925311A (en) 1986-02-10 1990-05-15 Teradata Corporation Dynamically partitionable parallel processors
US4736407A (en) 1986-04-08 1988-04-05 The United States Of America As Represented By The Secretary Of The Army Computer assisted graphic teleconferencing method and apparatus
US6032053A (en) 1995-07-19 2000-02-29 Pacific Communications Science, Inc. Signaling the type of incoming telephone calls
US6014706A (en) * 1997-01-30 2000-01-11 Microsoft Corporation Methods and apparatus for implementing control functions in a streamed video display system
US6047194A (en) 1997-09-23 2000-04-04 Telefonaktiebolaget L M Ericsson (Publ) Method, and associated apparatus, for selectively permitting transmission of packet data to a mobile terminal
US6608832B2 (en) 1997-09-25 2003-08-19 Telefonaktiebolaget Lm Ericsson Common access between a mobile communications network and an external network with selectable packet-switched and circuit-switched and circuit-switched services
US6061572A (en) 1997-12-15 2000-05-09 Telefonaktiebolaget L M Ericsson (Publ) Digital cellular telecommunications with short message service over the packet channel
US6374112B1 (en) 1998-04-03 2002-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Flexible radio access and resource allocation in a universal mobile telephone system
US6665711B1 (en) 1998-04-30 2003-12-16 Openwave Systems Inc. Method and apparatus for integrating narrowband and wideband data transports
US6067529A (en) 1998-08-12 2000-05-23 Ericsson Inc. System and method for sending a short message containing purchase information to a destination terminal
US6018662A (en) 1998-09-08 2000-01-25 Nortel Networks Corporation Method for performing progressive soft handoff in CDMA systems
US6857021B1 (en) 1998-10-30 2005-02-15 3Com Corporation Proximity-based registration on a data network telephony system
US20060114987A1 (en) 1998-12-21 2006-06-01 Roman Kendyl A Handheld video transmission and display
US6847632B1 (en) 1998-12-22 2005-01-25 Nortel Networks Limited Method and apparatus for digital cellular internet voice communications
US6675196B1 (en) 1999-01-08 2004-01-06 Amazon.Com, Inc. Universal protocol for enabling a device to discover and utilize the services of another device
US7076554B1 (en) 1999-06-11 2006-07-11 Nec Infrontia Corporation Internet service telephone communication connection method
US20020064274A1 (en) 1999-06-14 2002-05-30 Heikki Tuunanen Initiating a controlling service
US20020059416A1 (en) 1999-07-09 2002-05-16 Heikki Tuunanen Management of performance of intelligent network services
US20030055974A1 (en) 1999-08-24 2003-03-20 Kevin Brophy Systems and methods for providing unified multimedia communication services
US6782412B2 (en) 1999-08-24 2004-08-24 Verizon Laboratories Inc. Systems and methods for providing unified multimedia communication services
US6574326B1 (en) 1999-11-18 2003-06-03 Nokia Network Oy Method and system for minimizing transmission of optional parameters in an intelligent network environment
US6650705B1 (en) 2000-05-26 2003-11-18 Mitsubishi Electric Research Laboratories Inc. Method for encoding and transcoding multiple video objects with variable temporal resolution
US20040218571A1 (en) 2000-07-12 2004-11-04 Michael Pascazi System and method for cellphone to cell phone signal transmission via the internet
US20040076145A1 (en) 2000-12-22 2004-04-22 Timo Kauhanen Method and system for establishing a multimedia connection by negotiating capability in an outband control channel
US20020140726A1 (en) 2000-12-22 2002-10-03 Schwartz Richard L. Method and system for facilitating mediated communication
US20020181462A1 (en) 2001-04-24 2002-12-05 Sorin Surdila System and method for providing end-to-end quality of service (QoS) across multiple internet protocol (IP) networks
US20040261116A1 (en) 2001-07-03 2004-12-23 Mckeown Jean Christophe Broadband communications
US20030027569A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system for providing roaming between an internet protocol multimedia system and a circuit-switched domain
US20030027595A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Provision of services in a communication system including an interworking mobile switching center
US20030026245A1 (en) 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system including an interworking mobile switching center for call termination
US7024198B2 (en) 2001-08-23 2006-04-04 Siemens Aktiengellschaft Method for expediting a short message via a server when a communication participant of a communication network is not available
US6888828B1 (en) 2001-10-02 2005-05-03 Nokia Corporation System and method for providing at least one service obtained from a service network for a user in a packet switched communication network
US20050021494A1 (en) 2001-10-19 2005-01-27 Nokia Inc. Selective media capture via a communication device
US20050043020A1 (en) 2001-11-20 2005-02-24 Matti Lipsanen Mobile telecommunication networks and digital broadcasting services
US20040249962A1 (en) 2001-11-28 2004-12-09 Medialive, A Corporation Of France Method and system for accessing video and multimedia electronic mail
US6694145B2 (en) 2001-12-27 2004-02-17 Nokia Corporation Synchronization of signaling messages and multimedia content loading
US20030134640A1 (en) 2001-12-29 2003-07-17 Samsung Electronics Co., Ltd Apparatus and method for initiating a broadcast service by a mobile station in a mobile communication system
US20030134636A1 (en) * 2002-01-02 2003-07-17 Rangamani Sundar Method, system, and apparatus for a mobile station to sense and select a wireless local area network (WLAN) or a wide area mobile wireless network (WWAN)
US20050050194A1 (en) 2002-01-10 2005-03-03 Bernhard Honeisen Method and system for proxying a message
US20030144008A1 (en) 2002-01-28 2003-07-31 Rehkopf Thomas W. System and method for accessing computer services via a wireless network
US20050089020A1 (en) 2002-03-27 2005-04-28 Telefonaktiebolaget Lm Erisson (Publ) Charging in a communications network
US20030193426A1 (en) * 2002-04-12 2003-10-16 Alberto Vidal Apparatus and method to facilitate universal remote control
US20040019901A1 (en) 2002-04-29 2004-01-29 The Boeing Company Methodology for display/distribution of multiple content versions based on demographics
US20030210683A1 (en) 2002-05-07 2003-11-13 Koninklijke Kpn N.V. Telecommunication system
US7640038B2 (en) 2002-05-22 2009-12-29 Interdigital Technology Corporation Mobile unit having internet protocol functionality
US20040008669A1 (en) 2002-06-03 2004-01-15 Alcatel Telecommunication system with packet-switched-multimedia-session-to-circuit-switched-call transferral
US20050286531A1 (en) 2002-07-16 2005-12-29 Markku Tuohino Optimized routing between communication networks
US20040019539A1 (en) 2002-07-25 2004-01-29 3Com Corporation Prepaid billing system for wireless data networks
US20040043766A1 (en) 2002-08-27 2004-03-04 Nec Corporation System and method for informing that user is in or not in wireless LAN service
US20040048612A1 (en) 2002-09-09 2004-03-11 Kejio Virtanen Unbroken primary connection switching between communications services
US6950655B2 (en) 2002-10-01 2005-09-27 Interdigital Technology Corporation Method and system wherein handover information is broadcast in wireless local area networks
US20040062230A1 (en) 2002-10-01 2004-04-01 Nortel Networks Limited Integrating multimedia capabilities with legacy networks
US20040068574A1 (en) 2002-10-03 2004-04-08 Nokia Corporation WV-IMS relay and interoperability methods
US20040083195A1 (en) 2002-10-23 2004-04-29 Mccord Alan Wayne Method and system for enabling automated and real-time discovery of skills available to agents and systems in a multimedia communications network
US20040107143A1 (en) * 2002-11-29 2004-06-03 Aki Niemi Method for authorizing indirect content download
US20040127251A1 (en) 2002-12-16 2004-07-01 Thakkar Vivek V. Method and apparatus for mixed mode personal communication
EP1435748B1 (en) 2002-12-30 2006-03-29 France Telecom Handover between wireless networks of different technologies
US20060209768A1 (en) 2003-01-14 2006-09-21 Matsushita Electric Industrial Co., Ltd. Service in wlan inter-working, address management system, and method
US20040249887A1 (en) 2003-02-15 2004-12-09 Miguel-Angel Garcia-Martin Conversational bearer negotiation
US20040162892A1 (en) 2003-02-18 2004-08-19 Hsu Raymond T. Provisioning server information in a mobile station
US20040193725A1 (en) 2003-03-25 2004-09-30 Jose Costa-Requena Optimal location service for managing next hop addressing for messages associated with multiple address schemes
US20040193700A1 (en) 2003-03-25 2004-09-30 Ilkka Westman Service provisioning in a communication system
US20040205212A1 (en) 2003-03-31 2004-10-14 Nokia Corporation Method and system for forwarding a service-related information to a network user
US20060164550A1 (en) 2003-04-24 2006-07-27 Kyosuke Yoshimoto Video device, video module unit, and video device operation method
US20040219912A1 (en) 2003-04-29 2004-11-04 Klas Johansson Method and system for exchanging the capacity reports in a radio access network
US20070174471A1 (en) 2003-04-30 2007-07-26 Cedric Van Rossum Secure, continous, proxy-optimized, device-to-device data download reception system and method of use
US7194235B2 (en) 2003-06-03 2007-03-20 Nokia Corporation System, method, and apparatus for facilitating media content channels
US20040252673A1 (en) 2003-06-11 2004-12-16 Ejzak Richard Paul Server component redirection of new media path portion between packet-switched and circuit-switched portions of mobile switching center
US20070053343A1 (en) 2003-06-19 2007-03-08 Janne Suotula Conversational bearer negotiation
US20050025163A1 (en) 2003-07-28 2005-02-03 Nortel Networks Limited Mobility in a multi-access communication network
US20050047399A1 (en) 2003-08-29 2005-03-03 Sang-Do Lee Method and apparatus for providing voice and data services in a mobile communication system with various overlapped access networks
US7277416B1 (en) 2003-09-02 2007-10-02 Cellco Partnership Network based IP address assignment for static IP subscriber
US20050058125A1 (en) 2003-09-11 2005-03-17 Nokia Corporation IP-based services for circuit-switched networks
US20070033286A1 (en) 2003-09-15 2007-02-08 Ku-Bong Min Method for setting media streaming parameter of upnp-based network
US20050063329A1 (en) 2003-09-19 2005-03-24 Sang-Do Lee Data push service system and method using a heterogeneous network
US20080043717A1 (en) 2003-09-19 2008-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Exchange Protocol For Combinational Multimedia Services
US20050083909A1 (en) 2003-10-17 2005-04-21 Jarmo Kuusinen System, apparatus, and method for establishing circuit-switched communications via packet-switched network signaling
US20050114493A1 (en) * 2003-10-22 2005-05-26 Davide Mandato Context-aware automatic service discovery and execution engine in mobile ad-hoc networks
US7155305B2 (en) * 2003-11-04 2006-12-26 Universal Electronics Inc. System and methods for home appliance identification and control in a networked environment
US20060155850A1 (en) * 2003-11-25 2006-07-13 Matsushita Electric Industrial Co., Ltd. Networked mobile EPG service architecture
EP1545129A1 (en) 2003-12-16 2005-06-22 Hutchison Whampoa Three G IP (Bahamas) Limited Push to watch : a video person-to-person streaming application
US20070217349A1 (en) 2003-12-22 2007-09-20 Gabor Fodor System and Method for Multi-Access
US20070165599A1 (en) 2003-12-30 2007-07-19 Robert Skog Method and communication system for automatically discovering the common multimedia service capability
US8065402B2 (en) 2004-01-20 2011-11-22 International Business Machines Corporation Network management using short message service
US20050180394A1 (en) 2004-02-13 2005-08-18 Olaf Kautz Method for changing between a packet-oriented PTT session and a circuit-oriented telephone connection between at least two radio communication appliances, associated radio communication appliance, network component and radio communication system
US20050190772A1 (en) 2004-02-26 2005-09-01 Shang-Chih Tsai Method of triggering application service using filter criteria and IP multimedia subsystem using the same
US20050213606A1 (en) 2004-03-25 2005-09-29 Jiun-Yao Huang Method of triggering application service using response filter criteria and IP multimedia subsystem using the same
US20050237933A1 (en) 2004-03-30 2005-10-27 Pekka Marjelund Delivering services in a wireless communications system
US20050227681A1 (en) 2004-04-08 2005-10-13 Shenzhen Dianjing Technology Co. Ltd. Method and communication system of associated phone calling
US20050245261A1 (en) * 2004-04-14 2005-11-03 Ejzak Richard P Method of handing off a packet switched to a circuit switched call
US20050243870A1 (en) 2004-04-14 2005-11-03 Balogh Dan A Method of transferring call transition messages between network controllers of different radio technologies
US7301938B2 (en) 2004-04-14 2007-11-27 Lucent Technologies Inc. Method of transferring a packet switched to a circuit switched call
US20050271011A1 (en) 2004-06-07 2005-12-08 Nokia Inc. Vertical network handovers
US20060015812A1 (en) 2004-07-15 2006-01-19 Cingular Wireless Ii, Llc Using emoticons, such as for wireless devices
US20060025151A1 (en) 2004-07-28 2006-02-02 Jeyhan Karaoguz Handoff of a multimedia call session using background network scanning
US20060080407A1 (en) * 2004-10-12 2006-04-13 Motorola, Inc. Multimedia session establishment in a user entity having audio floor control
US20060083199A1 (en) 2004-10-15 2006-04-20 Yang Jianhao M System, method, and device for handing off between voice over internet protocol over wireless access sessions and CDMA circuit switched voice sessions
US20060140150A1 (en) 2004-11-05 2006-06-29 Interdigital Technology Corporation Wireless communication method and system for implementing media independent handover between technologically diversified access networks
US7729298B2 (en) 2004-11-08 2010-06-01 Motorola, Inc. Method and system for manipulating a shared object
US20080130637A1 (en) 2004-11-18 2008-06-05 Nishi Kant Maintaining Consistent Network Connections While Moving Through Wireless Networks
US20060104262A1 (en) 2004-11-18 2006-05-18 Azaire Networks Inc. Maintaining consistent network connections while moving through wireless networks
US20060120287A1 (en) 2004-12-03 2006-06-08 George Foti Seamless handoff for multimedia services
US20060120339A1 (en) 2004-12-08 2006-06-08 Oki Electric Industry Co., Ltd. Method of controlling quality of service for a wireless LAN base station apparatus
US7519075B2 (en) 2004-12-10 2009-04-14 Mediatek Inc. Method and system for serverless VoIP service in personal communication network
US20060126562A1 (en) 2004-12-14 2006-06-15 Huitao Liu Method and system for seamless service availability for multi-mode terminals in different access networks
EP1672893A1 (en) 2004-12-20 2006-06-21 Star Home GmbH Apparatus and method for pre-call notification of a callee
US20060155814A1 (en) 2004-12-31 2006-07-13 Sony Ericsson Mobile Communications Ab Media client architecture for networked communication devices
US20060149811A1 (en) * 2004-12-31 2006-07-06 Sony Ericsson Mobile Communications Ab Method for remotely controlling media devices via a communication network
US20070050510A1 (en) 2005-03-14 2007-03-01 Roamware, Inc. Session-based multimedia messaging service
US20060221903A1 (en) 2005-03-30 2006-10-05 Nokia Corporation Communication connection control mechanism in a core network ordered access change scenario
US20060246903A1 (en) 2005-04-29 2006-11-02 Samsung Electronics Co., Ltd. System and method for voice data handoff between cellular network and WiBro/WLAN network in heterogeneous network environment
US20060250578A1 (en) * 2005-05-06 2006-11-09 Pohl Garrick G Systems and methods for controlling, monitoring, and using remote applications
US20060256751A1 (en) 2005-05-11 2006-11-16 Cisco Technology, Inc. System and method for offering seamless connectivity across multiple devices in a communications environment
US20060258394A1 (en) 2005-05-11 2006-11-16 Dhillon Harry S Short message service encapsulation of supplementary service requests for IMS
US20060262806A1 (en) 2005-05-19 2006-11-23 Imed Bouazizi System and method for data delivery
US20070014281A1 (en) 2005-06-15 2007-01-18 Azaire Networks Voice call continuity application server between IP-CAN and CS networks
US20060291419A1 (en) 2005-06-22 2006-12-28 Sprint Spectrum L.P. Method and system for managing communication sessions during multi-mode mobile station handoff
US20060291488A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. System and method of interworking non-IMS and IMS networks to create new services utilizing both networks
US20060291489A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. System and method to mediate delivery of legacy, non-IMS services into an IMS network
US20060291412A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A Associated device discovery in IMS networks
US20110164563A1 (en) 2005-06-24 2011-07-07 Aylus Networks, Inc. Method of Avoiding or Minimizing Cost of Stateful Connections Between Application Servers and S-CSCF Nodes in an IMS Network with Multiple Domains
US7864936B2 (en) 2005-06-24 2011-01-04 Aylus Networks, Inc. Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
US20060291487A1 (en) 2005-06-24 2006-12-28 Aylus Networks, Inc. IMS networks with AVS sessions with multiple access networks
US20060291484A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
US20060291437A1 (en) 2005-06-24 2006-12-28 Naqvi Shamim A System and method to provide dynamic call models for users in an IMS network
US20070008951A1 (en) 2005-06-24 2007-01-11 Naqvi Shamim A Mediation system and method for hybrid network including an IMS network
US20070008913A1 (en) 2005-06-24 2007-01-11 Naqvi Shamim A Method and system for provisioning IMS networks with virtual service organizations having distinct service logic
WO2007010070A2 (en) 2005-07-20 2007-01-25 Createcna Xxi S.L. System for live television broadcasting from a mobile telephone
US20070067807A1 (en) 2005-09-16 2007-03-22 O'neil Douglas Methods, systems, and computer program products for providing multimedia information services over a communication network
US20070066347A1 (en) 2005-09-19 2007-03-22 Silverbrook Research Pty Ltd Printing a puzzle using a mobile device
US7637424B2 (en) 2005-09-19 2009-12-29 Silverbrook Research Pty Ltd Printing audio information using a mobile device
US20090092109A1 (en) * 2005-12-19 2009-04-09 Torbjorn Cagenius Method and Apparatus for Enabling Discovery Within a Home Network
US20070143488A1 (en) * 2005-12-20 2007-06-21 Pantalone Brett A Virtual universal plug and play control point
US20070143489A1 (en) * 2005-12-20 2007-06-21 Pantalone Brett A Communication network device for universal plug and play and Internet multimedia subsystems networks
US20070155310A1 (en) 2005-12-31 2007-07-05 Rob Borcic Interrupting and resuming a media player
WO2007117730A2 (en) 2006-01-13 2007-10-18 Dilithium Networks Pty Ltd. Interactive multimedia exchange architecture and services
US20070197227A1 (en) 2006-02-23 2007-08-23 Aylus Networks, Inc. System and method for enabling combinational services in wireless networks by using a service delivery platform
US20070207782A1 (en) 2006-03-06 2007-09-06 Tran Bao Q Multimedia telephone
US20080291905A1 (en) 2006-05-16 2008-11-27 Kiran Chakravadhanula Systems and Methods for Real-Time Cellular-to-Internet Video Transfer
US20080092178A1 (en) 2006-10-11 2008-04-17 Cingular Wireless Ii, Llc Streaming video
US7720489B2 (en) 2006-10-12 2010-05-18 At&T Mobility Ii Llc Network initiated USSD in mixed networks
US20080162637A1 (en) 2006-11-03 2008-07-03 At&T Bls Intellectual Property, Inc. Application services infrastructure for next generation networks including a notification capability and related methods and computer program products
US7856226B2 (en) 2007-04-17 2010-12-21 Aylus Networks, Inc. Systems and methods for IMS user sessions with dynamic service selection
US8170534B2 (en) 2007-04-17 2012-05-01 Aylus Networks, Inc. Systems and methods for user sessions with dynamic service selection

Non-Patent Citations (12)

* Cited by examiner, † Cited by third party
Title
Definition of ‘proxy’ from dictionary.com. *
Definition of 'proxy' from dictionary.com. *
European Search Report for European Patent Application No. 08769004.6 mailed Jun. 21, 2012. 7 pages.
European Search Report for European Patent Application No. EP08746133 mailed Jun. 25, 2010. 8 pages.
GSM Association: "Video Share Service Definition 2.0." Mar. 27, 2007. XP002585831. http://www.gsmworld.com/documents/se41.pdf>. Retrieved on Jun. 2, 2010. 28 pages.
International Search Report and Written Opinion, International Application No. PCT/US08/60656, Aylus Networks, Inc., Jul. 2, 2008, 8 pages.
International Search Report for Application No. PCT/US08/57367, Aylus Networks, Inc., Aug. 8, 2008, 7 pages.
International Search Report for International Application No. PCT/US07/04854, Aylus Networks, Inc., Jan. 31, 2008 (3 pages).
International Search Report, International Application No. PCT/US 06/24619, date mailed Feb. 14, 2007, 2 pages.
International Search Report, International Application No. PCT/US 06/24624, mailed Apr. 3, 2007, 1 pages.
Nokia Corporation: "Video Sharing, Enrich Your Voice Call with Video." Nov. 1, 2004. XP002336424. 12 pages.
OSGi Service Platform, Mar. 2003, The Open Services Gateway Initiative, Release 3, pp. 345-346, 505, 513-526. *

Cited By (146)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10681100B2 (en) * 2007-08-17 2020-06-09 Huawei Technologies Co., Ltd. Method, user equipment and application server for adding media stream of multimedia session
US10237146B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Adaptive ambient services
US10057141B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Proxy system and method for adaptive ambient services
US9198076B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with power-control-state-based wireless network access policy for background applications
US9198117B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Network system with common secure wireless message service serving multiple applications on multiple wireless devices
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9198074B2 (en) * 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service
US9204374B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Multicarrier over-the-air cellular network activation server
US9204282B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9215613B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list having limited user control
US9215159B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Data usage monitoring for media data services used by applications
US9220027B1 (en) 2009-01-28 2015-12-22 Headwater Partners I Llc Wireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications
US9225797B2 (en) 2009-01-28 2015-12-29 Headwater Partners I Llc System for providing an adaptive wireless ambient service to a mobile device
US9232403B2 (en) 2009-01-28 2016-01-05 Headwater Partners I Llc Mobile device with common secure wireless message service serving multiple applications
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9258735B2 (en) 2009-01-28 2016-02-09 Headwater Partners I Llc Device-assisted services for protecting network capacity
US9271184B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Wireless end-user device with per-application data limit and traffic control policy list limiting background application traffic
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9277445B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service
US9277433B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with policy-based aggregation of network activity requested by applications
US9319913B2 (en) 2009-01-28 2016-04-19 Headwater Partners I Llc Wireless end-user device with secure network-provided differential traffic control policy list
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9386121B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc Method for providing an adaptive wireless ambient service to a mobile device
US9386165B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc System and method for providing user notifications
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9491199B2 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9491564B1 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Mobile device and method with secure network messaging for authorized components
US9521578B2 (en) 2009-01-28 2016-12-13 Headwater Partners I Llc Wireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy
US9532261B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc System and method for wireless network offloading
US9532161B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc Wireless device with application data flow tagging and network stack-implemented network access policy
US9544397B2 (en) 2009-01-28 2017-01-10 Headwater Partners I Llc Proxy server for providing an adaptive wireless ambient service to a mobile device
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565543B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Device group partitions and settlement platform
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9591474B2 (en) 2009-01-28 2017-03-07 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9609459B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Network tools for analysis, design, testing, and production of services
US9609544B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Device-assisted services for protecting network capacity
US9615192B2 (en) 2009-01-28 2017-04-04 Headwater Research Llc Message link server with plural message delivery triggers
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9674731B2 (en) 2009-01-28 2017-06-06 Headwater Research Llc Wireless device applying different background data traffic policies to different device applications
US9705771B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Attribution of mobile device data traffic to end-user application based on socket flows
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9749899B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications
US9749898B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9769207B2 (en) 2009-01-28 2017-09-19 Headwater Research Llc Wireless network service interfaces
US9819808B2 (en) 2009-01-28 2017-11-14 Headwater Research Llc Hierarchical service policies for creating service usage data records for a wireless end-user device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9866642B2 (en) 2009-01-28 2018-01-09 Headwater Research Llc Wireless end-user device with wireless modem power state control policy for background applications
US9942796B2 (en) 2009-01-28 2018-04-10 Headwater Research Llc Quality of service for device assisted services
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9973930B2 (en) 2009-01-28 2018-05-15 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10028144B2 (en) 2009-01-28 2018-07-17 Headwater Research Llc Security techniques for device assisted services
US10237773B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Device-assisted services for protecting network capacity
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10064033B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Device group partitions and settlement platform
US10070305B2 (en) 2009-01-28 2018-09-04 Headwater Research Llc Device assisted services install
US10080250B2 (en) 2009-01-28 2018-09-18 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10165447B2 (en) 2009-01-28 2018-12-25 Headwater Research Llc Network service plan design
US10171990B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Service selection set publishing to device agent with on-device service selection
US10171988B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Adapting network policies based on device service processor configuration
US10171681B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Service design center for device assisted services
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US20150215815A1 (en) * 2009-01-28 2015-07-30 Headwater Partners I Llc Device-Assisted Services for Protecting Network Capacity
US9641957B2 (en) 2009-01-28 2017-05-02 Headwater Research Llc Automated device provisioning and activation
US9198075B2 (en) * 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10321320B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Wireless network buffered message system
US10320990B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US12101434B2 (en) 2009-01-28 2024-09-24 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10326675B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Flow tagging for service policy implementation
US10462627B2 (en) 2009-01-28 2019-10-29 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10536983B2 (en) 2009-01-28 2020-01-14 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10582375B2 (en) 2009-01-28 2020-03-03 Headwater Research Llc Device assisted services install
US10681179B2 (en) 2009-01-28 2020-06-09 Headwater Research Llc Enhanced curfew and protection associated with a device group
US20150223101A1 (en) * 2009-01-28 2015-08-06 Headwater Partners I Llc Wireless End-User Device With Differential Traffic Control Policy List Applicable to One of Several Wireless Modems
US10694385B2 (en) 2009-01-28 2020-06-23 Headwater Research Llc Security techniques for device assisted services
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10716006B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US10749700B2 (en) 2009-01-28 2020-08-18 Headwater Research Llc Device-assisted services for protecting network capacity
US10771980B2 (en) 2009-01-28 2020-09-08 Headwater Research Llc Communications device with secure data path processing agents
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10791471B2 (en) 2009-01-28 2020-09-29 Headwater Research Llc System and method for wireless network offloading
US10798254B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Service design center for device assisted services
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10798558B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Adapting network policies based on device service processor configuration
US10803518B2 (en) 2009-01-28 2020-10-13 Headwater Research Llc Virtualized policy and charging system
US11985155B2 (en) 2009-01-28 2024-05-14 Headwater Research Llc Communications device with secure data path processing agents
US11973804B2 (en) 2009-01-28 2024-04-30 Headwater Research Llc Network service plan design
US10834577B2 (en) 2009-01-28 2020-11-10 Headwater Research Llc Service offer set publishing to device agent with on-device service selection
US11966464B2 (en) 2009-01-28 2024-04-23 Headwater Research Llc Security techniques for device assisted services
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10848330B2 (en) 2009-01-28 2020-11-24 Headwater Research Llc Device-assisted services for protecting network capacity
US10855559B2 (en) 2009-01-28 2020-12-01 Headwater Research Llc Adaptive ambient services
US10869199B2 (en) 2009-01-28 2020-12-15 Headwater Research Llc Network service plan design
US10985977B2 (en) 2009-01-28 2021-04-20 Headwater Research Llc Quality of service for device assisted services
US11039020B2 (en) 2009-01-28 2021-06-15 Headwater Research Llc Mobile device and service management
US11096055B2 (en) 2009-01-28 2021-08-17 Headwater Research Llc Automated device provisioning and activation
US11134102B2 (en) 2009-01-28 2021-09-28 Headwater Research Llc Verifiable device assisted service usage monitoring with reporting, synchronization, and notification
US11190545B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Wireless network service interfaces
US11190427B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Flow tagging for service policy implementation
US11190645B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11219074B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US11228617B2 (en) 2009-01-28 2022-01-18 Headwater Research Llc Automated device provisioning and activation
US11337059B2 (en) 2009-01-28 2022-05-17 Headwater Research Llc Device assisted services install
US11363496B2 (en) 2009-01-28 2022-06-14 Headwater Research Llc Intermediate networking devices
US11405429B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Security techniques for device assisted services
US11405224B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Device-assisted services for protecting network capacity
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11425580B2 (en) 2009-01-28 2022-08-23 Headwater Research Llc System and method for wireless network offloading
US11477246B2 (en) 2009-01-28 2022-10-18 Headwater Research Llc Network service plan design
US11494837B2 (en) 2009-01-28 2022-11-08 Headwater Research Llc Virtualized policy and charging system
US11516301B2 (en) 2009-01-28 2022-11-29 Headwater Research Llc Enhanced curfew and protection associated with a device group
US11533642B2 (en) 2009-01-28 2022-12-20 Headwater Research Llc Device group partitions and settlement platform
US11538106B2 (en) 2009-01-28 2022-12-27 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US11563592B2 (en) 2009-01-28 2023-01-24 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US11570309B2 (en) 2009-01-28 2023-01-31 Headwater Research Llc Service design center for device assisted services
US11582593B2 (en) 2009-01-28 2023-02-14 Head Water Research Llc Adapting network policies based on device service processor configuration
US11589216B2 (en) 2009-01-28 2023-02-21 Headwater Research Llc Service selection set publishing to device agent with on-device service selection
US11665186B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Communications device with secure data path processing agents
US11665592B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US11968234B2 (en) 2009-01-28 2024-04-23 Headwater Research Llc Wireless network service interfaces
US11750477B2 (en) 2009-01-28 2023-09-05 Headwater Research Llc Adaptive ambient services
US11757943B2 (en) 2009-01-28 2023-09-12 Headwater Research Llc Automated device provisioning and activation
US11923995B2 (en) 2009-01-28 2024-03-05 Headwater Research Llc Device-assisted services for protecting network capacity
US11743717B2 (en) 2013-03-14 2023-08-29 Headwater Research Llc Automated credential porting for mobile devices
US10834583B2 (en) 2013-03-14 2020-11-10 Headwater Research Llc Automated credential porting for mobile devices
US10171995B2 (en) 2013-03-14 2019-01-01 Headwater Research Llc Automated credential porting for mobile devices
US10805200B2 (en) 2013-06-25 2020-10-13 Google Llc Efficient communication for devices of a home network
US10320763B2 (en) * 2013-06-25 2019-06-11 Google Inc. Efficient communication for devices of a home network
US20170094551A1 (en) * 2015-09-30 2017-03-30 Intel IP Corporation Interference mitigation by a scalable digital wireless modem
US9843959B2 (en) * 2015-09-30 2017-12-12 Intel IP Corporation Interference mitigation by a scalable digital wireless modem

Also Published As

Publication number Publication date
US20060294244A1 (en) 2006-12-28
US7724753B2 (en) 2010-05-25

Similar Documents

Publication Publication Date Title
US12114382B2 (en) Associated device discovery in IMS networks
USRE44412E1 (en) Digital home networks having a control point located on a wide area network
CA2613478C (en) System and method of device discovery and control in ip multimedia subsystem networks
US20060291488A1 (en) System and method of interworking non-IMS and IMS networks to create new services utilizing both networks
US20060291487A1 (en) IMS networks with AVS sessions with multiple access networks
US20060291489A1 (en) System and method to mediate delivery of legacy, non-IMS services into an IMS network
US8483373B2 (en) Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
EP1892897B2 (en) A cross-domain routing control method
US7672297B2 (en) Mediation system and method for hybrid network including an IMS network
US7561535B2 (en) System and method for providing dynamic call models for users as function of the user environment in an IMS network
US7792528B2 (en) Method and system for provisioning IMS networks with virtual service organizations having distinct service logic
US8351393B2 (en) Switching of multimedia sessions from a mobile terminal
US20080317010A1 (en) System and method for signaling optimization in ims services by using a service delivery platform
WO2006102830A1 (en) A method for terminal identifying capability interaction route control while ims and cs are coinstantaneous
CN1984121A (en) Network element with interconnecting function, CSI terminal, IMS terminal interconnecting system and method
US8751680B2 (en) Apparatus, method and computer program for seamless session transfer
WO2023185854A1 (en) Information processing method and apparatus, and communication device and storage medium
WO2007002485A2 (en) Interworking non-ims and ims networks utilizing both networks to create new services

Legal Events

Date Code Title Description
FPAY Fee payment

Year of fee payment: 4

IPR Aia trial proceeding filed before the patent and appeal board: inter partes review

Free format text: TRIAL NO: IPR2014-01566

Opponent name: APPLE, INC.

Effective date: 20140929

Free format text: TRIAL NO: IPR2014-01565

Opponent name: APPLE, INC.

Effective date: 20140929

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.)

IPRC Trial and appeal board: inter partes review certificate

Kind code of ref document: K1

Free format text: INTER PARTES REVIEW CERTIFICATE; TRIAL NO. IPR2014-01565, SEP. 29, 2014INTER PARTES REVIEW CERTIFICATE FOR PATENT RE44,412, ISSUED AUG. 6, 2013, APPL. NO. 13/232,432, SEP. 14, 2011INTER PARTES REVIEW CERTIFICATE ISSUED FEB. 21, 2018

Effective date: 20180221

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.)