Patent Publication Number: US-2023153399-A1

Title: System and method for providing multimedia digital rights transfer

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/294,203 filed on Mar. 6, 2019, which is a continuation of and claims priority to U.S. patent application Ser. No. 13/667,579 filed on Nov. 2, 2012 (now U.S. Pat. No. 10,268,805), which is a continuation of and claims priority to U.S. patent application Ser. No. 12/693,521 filed on Jan. 26, 2010 (now U.S. Pat. No. 8,312,158). The contents of each of the foregoing are hereby incorporated by reference into this application as if set forth herein in full. 
    
    
     FIELD OF THE DISCLOSURE 
     The present disclosure relates to the transfer of digital multimedia rights. 
     BACKGROUND OF THE DISCLOSURE 
     Digital rights management (DRM) is a generic term for access control technologies that can be used by hardware manufacturers, publishers, copyright holders and individuals to try to impose limitations on the usage of digital content and devices. The term is used to describe any technology which inhibits uses (legitimate or otherwise) of digital content that were not desired or foreseen by the content provider. The term generally doesn&#39;t refer to other forms of copy protection which can be circumvented without modifying the file or device, such as serial numbers or keyfiles. It can also refer to restrictions associated with specific instances of digital works or devices. A user&#39;s multimedia digital rights (e.g. television service package) are usually associated with a single device or a fixed location, for example the user&#39;s home television set top box. Thus when a person leaves home they leave their digital multimedia rights behind. 
     BRIEF DESCRIPTION OF THE DRAWINGS 
       FIG.  1    depicts an illustrative embodiment of a system for transferring digital multimedia rights data; 
       FIG.  2    depicts an illustrative embodiment of a system for transferring digital multimedia rights data; and 
       FIG.  3    is an illustrative embodiment of a machine for performing functions disclosed in an illustrative embodiment. 
    
    
     DETAILED DESCRIPTION 
     This disclosure describes an illustrative embodiment that enables a user&#39;s Multimedia Digital Rights (e.g. for Video) to follow them to other locations, for example when visiting a friend&#39;s home, or in a hotel while traveling. Components include the owner&#39;s end user devices (fixed and mobile) as well as core network of service providers. System, methods and computer program components are described herein for supporting a Multimedia Digital Rights transfer request, authorization, validation, provisioning, and canceling. Consideration is provided for manual as well as automatic transfer and re-provisioning of multimedia digital rights to other location and other end user devices, which may take into consideration information regarding an end user&#39;s change of location. 
     In another particular illustrative embodiment, a method for transferring digital multimedia rights is disclosed, the method including but not limited to receiving at a digital multimedia rights server, from a source end user device associated with a source end user, a request for a transfer of a source set of digital multimedia rights associated with the source end user; determining a destination end user associated with a destination end user device to which the digital multimedia rights will be transferred; requesting permission from the destination end user to transfer the digital multimedia rights to the destination end user device; and if the permission is received from the destination end user, canceling the source set of digital multimedia rights associated with the source end user and transferring the source set of digital multimedia rights associated with the source end user to the destination end user device. In another particular embodiment of the method, the transferring further includes but is not limited to merging the source set of digital multimedia rights with a destination set of digital multimedia rights associated with destination end user at the destination end user device. 
     In another particular embodiment of the method, the method further includes but not limited to automatically transferring the source set of digital multimedia rights to the destination end user device when an end user device associated with the source end user device designated by the source end user in a source end user profile, moves physically proximate to an end user device physical location associated with the destination end user. In another particular embodiment of the method, the transferring the digital multimedia rights further includes but is not limited to transferring to the destination end user device, less than all of the digital multimedia rights associated with the source end user. 
     In another particular embodiment of the method, the method further includes but not limited to generating an inter carrier transfer data token including but not limited to data indicating the source end user, source end user device, source end user carrier, source end user digital multimedia rights and destination end user; and sending the inter carrier transfer token data to an inter carrier token server for arbitration and transfer of the source digital multimedia rights to the destination end user device, wherein the source end user carrier is different from a carrier for the destination end user. 
     In another illustrative embodiment, a computer program product useful for transferring digital multimedia rights is disclosed, the computer program product including but not limited to a computer readable medium; a computer program including but not limited to computer executable instructions embedded in the computer readable medium, the computer program further including but not limited to instructions to receive at a digital multimedia rights server, from a source end user device associated with a source end user, a request for a transfer of a source set of digital multimedia rights associated with the source end user; instructions to determine a destination end user associated with a destination end user device to which the digital multimedia rights will be transferred; instructions to request permission from the destination end user to transfer the digital multimedia rights to the destination end user device; and instructions to, if the permission is received from the destination end user, cancel the source set of digital multimedia rights associated with the source end user and transferring the source set of digital multimedia rights associated with the source end user to the destination end user device. 
     In another particular embodiment of the computer program product, the instructions to transfer further include but not limited to instructions to merge the source set of digital multimedia rights with a destination set of digital multimedia rights associated with destination end user at the destination end user device. In another particular embodiment of the computer program product, the computer program further including but not limited to instructions to automatically transferring the source set of digital multimedia rights to the destination end user device when an end user device associated with the source end user device designated by the source end user in a source end user profile, moves physically proximate to an end user device physical location associated with the destination end user. In another particular embodiment of the computer program product, the instructions to transfer the digital multimedia rights further include but not limited to instructions to transfer to the destination end user device, less than all of the digital multimedia rights associated with the source end user. 
     In another particular embodiment of the computer program product, the computer program further includes but is not limited to instructions to generate an inter carrier transfer data token including but not limited to data indicating the source end user, source end user device, source end user carrier, source end user digital multimedia rights and destination end user; and instruction to send the inter carrier transfer token data to an inter carrier token server for arbitration and transfer of the source digital multimedia rights to the destination end user device, wherein the source end user carrier is different from a carrier for the destination end user. 
     In another illustrative embodiment, a system useful for transferring digital multimedia rights is disclosed, the system including but not limited to a processor; a computer readable medium; and a computer program including but not limited to computer executable instructions embedded in the computer readable medium, the computer program further including but not limited to instructions to receive at a digital multimedia rights server, from a source end user device associated with a source end user, a request for a transfer of a source set of digital multimedia rights associated with the source end user; instructions to determine a destination end user associated with a destination end user device to which the digital multimedia rights will be transferred; instructions to request permission from the destination end user to transfer the digital multimedia rights to the destination end user device; and instructions to, if the permission is received from the destination end user, cancel the source set of digital multimedia rights associated with the source end user and transferring the source set of digital multimedia rights associated with the source end user to the destination end user device. In another particular embodiment of the system, instructions to transfer further include but not limited to instructions to merge the source set of digital multimedia rights with a destination set of digital multimedia rights associated with destination end user at the destination end user device. In another particular embodiment of the system, the computer program further including but not limited to instructions to automatically transferring the source set of digital multimedia rights to the destination end user device when an end user device associated with the source end user device designated by the source end user in a source end user profile, moves physically proximate to an end user device physical location associated with the destination end user. In another particular embodiment of the system, the instructions to transfer the digital multimedia rights further include but not limited to instructions to transfer to the destination end user device, less than all of the digital multimedia rights associated with the source end user. 
     In another particular embodiment of the system, the computer program further including but not limited to instructions to generate an inter carrier transfer data token including but not limited to data indicating the source end user, source end user device, source end user earlier, source end user digital multimedia rights and destination end user; and instruction to send the inter carrier transfer token data to an inter carrier token server for arbitration and transfer of the source digital multimedia rights to the destination end user device, wherein the source end user carrier is different from a carrier for the destination end user. 
     Turning now to  FIG.  1   , in an illustrative embodiment an internet protocol television (IPTV) network  102  including but not limited to a vide head office (VHO)  104 , a digital rights media server  108  and end user profile server  106 . Each server and end user device in this disclosure are equipped with an processor  130 , computer readable memory  132  and data base  134  for arranging data used by the processor and stored in the computer readable medium. 
     The end user profile server contains a data base  134  of end user profiles that indicates the identify of each end user in the IPTV system, one or more end user devices associated with each of the end users and digital rights management data indicating what digital rights are granted to each end user on each end user device. For example, an end user Joe  116  has a television subscription package from his service provider that includes a premium sports channel. It&#39;s Saturday afternoon, Joe is at his friend Bob&#39;s  122  house, and they both really want to watch the big game that is about to be aired. Bob has the same television service provider as Joe, but doesn&#39;t subscribe to the premium sports channel, which is needed to watch the game. Joe runs an application of an illustrative embodiment of the present invention on his cell phone  117  that requests his digital rights service package to be made available by his service provider at Bob&#39;s house. In an illustrative embodiment, the application is very user friendly. The application knows Joe&#39;s identity, and deduces where Joe wants his digital rights transferred on the basis of Joe&#39;s location (which the application deduces from Joe&#39;s cell phone.) Joe&#39;s service provider authenticates and validates Joe&#39;s request to transfer his digital rights to an end user device such as a set top box at Bob&#39;s house. 
     The service provider identifies Bob and sends a message to Bob&#39;s current end user device, such as the set top box  118  at Bob&#39;s house. Bob receives a pop up message on his set top box display  123 , typically a television asking if Bob accepts letting Joe transfer Joe&#39;s multimedia digital rights, and Bob agrees by responding to the pop menu via his television remote control. The service provider manages the needed provisioning adjustments in the service provider data base  134  at the IPTV network for end user profiles which includes but is not limited to the digital right grants for all end users, including Bob and Joe. The service provider via digital rights transfer server  108  then grants the digital rights transfer. This makes Joe&#39;s digital rights available on Bob&#39;s television (in addition to Bob&#39;s rights which are temporarily merged with Joe&#39;s in the service provider database). At essentially the same time, Joe&#39;s multimedia digital rights that have been transferred to Bob&#39;s house are suspended at Joe&#39;s house. Joe happily gets to watch the big game. When Joe&#39;s leaves Sam&#39;s house, the digital rights transfer is cancelled as Bob&#39;s house and re-provisioned as enable back at Joe&#39;s house. In another illustrative embodiment, Joe can transfer a subset of his digital rights to Bob&#39;s house, for example, transferring only the sports package to Bob&#39;s house and leaving the multimedia digital rights to the movie package at home for his wife to watch a movie on the movie package, while Joe is at Bob&#39;s house watching the game. 
     In another illustrative embodiment, Joe can select a particular multimedia digital right to a particular end user device, associated with himself or with another end user. Thus, Joe can transfer the sports package on his home set top box to his cell phone or to Bob&#39;s cell phone so that they can watch the big football game from a mobile location. In another illustrative embodiment, Joe and Bob have different service providers  102  and  103  respectively, for their cell phones and their internet/multimedia providers. In this case, a request for a transfer of multimedia digital rights generates an inter carrier token that goes through a inter carrier service exchange server  106  or to identify Joe and Bob&#39;s carriers and allows both carriers to participate by re-provisioning and de-provisioning Joe&#39;s digital multimedia rights when he requests a transfer of his digital multimedia rights to Bob&#39;s set top box or to Bob&#39;s or his own cell phone. 
     Thus, a request to transfer digital multimedia rights received by a first carrier  102  for rights to be transferred to a second carrier  103  is handled by a inter carrier data token generated by the first carrier. The inter carrier data token contains data that indicates a source end user (Joe) and destination end user (Sam), their carrier affiliation and the source and destination&#39;s end users&#39; digital multimedia rights. Thus carrier A receives a request from Joe to transfer rights to Bob&#39;s set top box which is serviced by carrier B. Carrier A generates a transfer request message including inter carrier exchange data toke and sends it to the inter carrier exchange server  101  which decodes the token data and informs carrier B of the transfer request. Thus carrier A and carrier B communicate with the inter carrier exchange token server to carry out the transfer of digital multimedia rights from Joe&#39;s set top box to Bob&#39;s set top box or Bob&#39;s cell phone. 
     In a particular illustrative embodiment, a system is provided including but not limited to several components, which support functions to collectively provide the service functionality provided in a particular illustrative embodiment. In various particular embodiments, different computer programs and methods may be used to enable functionality in the components and end user devices. Components and end user devices include but are not limited to the user devices (e.g. Netbook, Cell Phone, PC, etc.), the service provider&#39;s Access Network  110  (e.g., set top box, home gateway  116 , femtocell  120 , etc.), and the service provider&#39;s Core Network (e.g. Video Application Server, Customer Service Profile, Video Head Office, etc.). Key functions for which methods are provided include but are not limited to enabling a multimedia digital rights transfer request from the user to the service provider. This transfer request may be manually invoked by the end user from an end user device, or automatically triggered, for example, when an end user has indicated in their service profile in the end user profile in the service provider&#39;s data base and the accessible from the inter service providers token server, that whenever I&#39;m (a first end user) is at Bob&#39;s House (a second end user), please transfer some or all of my multimedia digital rights to Bob&#39;s set top box (a first end user device for the second end user) house or Bob&#39;s cell phone (a second end user device for the second end user). Some or all of an end user&#39;s multimedia digital rights may be transferred, depending on the end user&#39;s preferences. Authenticating, and validating the multimedia Digital Rights transfer request. Validation may include confirming the location of the user. Acceptance of the multimedia Digital Rights Transfer Request by the destination user. 
     The request is be agreed upon by the party (Sam) to whom the multimedia digital rights are being transferred. Provisioning the multimedia digital rights transfer by the service provider. The first end user&#39;s multimedia digital rights may be merged with the multimedia digital rights of the visited friend, the second end user. The first end user&#39;s multimedia digital rights transfer may be terminated manually by the first or second end user, on the basis of duration, or (automatically) when the first end user leaves his friend&#39;s house, the second end user. Turning now to  FIG.  2   , as shown in  FIG.  2   , an illustrative message exchange scenario  200  is depict in which the source end user&#39;s digital rights transfer is initiated by a digital rights transfer request being sent from the user to the user&#39;s service provider. Information provided i n the digital rights transfer request can include the following origination identification e.g. the first or source end user&#39;s account name, e.g. the source end user&#39; s cell phone identity (e.g. MSISDN). MSISDN is a number uniquely identifying an end user subscription in a GSM or UNITS mobile network. Simply put, it is the telephone number to the SIM card in a mobile/cellular phone. The abbreviation has several interpretations, most common one being “Mobile Subscriber Integrated Services Digital Network Number. The MSISDN together with IMSI are two important numbers used to identify a mobile subscriber. The former identifies the SIM, i.e. the card that is inserted into the mobile phone, while the latter is used to route calls to the subscriber. IMSI is often used as a key in the HLR (“subscriber database”) and MSISDN is the number normally dialed to connect a call to the mobile phone. A SIM is uniquely associated to an IMSI, while the MSISDN can change in time (e.g. due to number portability), i.e. different MSISDNs can be associated to the SIM. 
     If the source end user&#39;s cell phone identity is used, a mapping may be needed by the service provider between the cell phone identity and the identity used for television subscription rights. When the cell phone service provider (carrier) and television service provider (carrier) are different carriers, an inter carrier data token is generated by the carrier receiving the transfer request, identifying the source and destination end users, television a and cell phone carriers, transfer request data indicating what rights are being transfer and to where (end user, end user device) and sent to the inter carrier server. 
     The inter carrier server functionality, including but not limited to a computer program product having a computer program of computer executable instructions embedded in a computer readable medium at the inter carrier server, arbitrates between carriers which re-provision and de-provision digital multimedia rights based on the transfer request defined in the inter carrier data token. It may be preferable for the Originating Identification to be provided as the television subscription identity for an end user profile for the source or requesting end user. Security Information e.g. a PIN, e.g. social security number, Destination Identification, e.g. the friend&#39;s account name (destination end user) e.g. the friend&#39;s address, e.g. the friend&#39;s cell phone identity (e.g. MSISDN), e.g. the user&#39;s current location (address or geographic coordinates), the service provider may require the user to be at the destination location. Default values for some or all of the needed information may be automatically provided. If the digital rights transfer request is made by user on the source end user&#39;s cell phone (e.g. using a client computer program in the cell phone), the client computer program may know some or all of the needed information (e.g. end user&#39;s identity, security information, destination=current location). 
     The digital rights transfer request can be originated by the first or source end user by any one of several methods, including using a mobile device (e.g. cell phone, net book) or fixed device (e.g. wireline phone) to call an interactive voice responder (IVR) provided by the service provider. The user identity may be automatically provided (e.g. calling party identity information), or may be manually provided by the user security information may be manually or verbally provided by the user, the service provider may know or be able to derive the user&#39;s location (mobile location) e.g. due to the user&#39;s cell phone&#39;s location e.g. registration on Bob&#39;s femtocell, attachment to WiFi access point, e.g. base station triangulation, e.g. GPS coordinates the correlation between the user&#39;s location and the destination (friend&#39;s address, identity). Using an application (e.g. widget, or client, or browser) that resides in a device (e.g. cell phone, net book, laptop, PC, IPTV, etc.) that may belong to the user or the user&#39;s friend and communicates with a server in the service provider&#39;s network (e.g. access network, core network, web, etc.). In telecommunications, a femtocell, originally known as an Access Point Base Station-is a small cellular base station, typically designed for use in a home or small business. It connects to the service provider&#39;s network via broadband (such as DSL or cable); current designs typically support 2 to 4 active mobile phones in a residential setting. A femtocell allows service providers to extend service coverage indoors, especially where access would otherwise be limited or unavailable. 
     Note that an application (client program) running on the user&#39;s cell phone is attractive because the user is likely to have the cell phone or other portable device with them when they are away from their home, and this approach doesn&#39;t impose any requirements on the visited user&#39;s devices. Note that the application could be intelligent, know or predict the desired information, and provide the needed information with minimal or no interaction with the user. For example, the application may be able to determine or deduce the origination Identification information as the identity of the owner of the device upon which the request is being originated (e.g. the user&#39;s cell phone). Security Information as previously provided and securely stored (encrypted, etc.) on the originating user&#39;s device. Destination Identification as a function of the user&#39;s current location, or last used destination, or cyclic calendar information (recurring event), or other information previously provided by the user. If, for example, the digital multimedia rights transfer request is provided from an application on the source end user user&#39;s cell phone, and the source end user&#39;s cell phone is registered on the friend&#39;s (destination end user) femtocell, it may be deduced that the originating identification information is that of the cell phone user (source end user), the security information is that of the cell phone user, the destination identification information is that of the femtocell owner. In this particular scenario, no information needs to be manually entered by the user. Furthermore, the service provider may automatically offer the digital rights transfer service to the user when their cell phone registers on their friend&#39;s femtocell. The desired functionality may be implemented using a client-server model whereby user interfacing functionality is provided by a client that runs in a user device, and service provider functionality is provided by one or more network based application servers. 
     The digital rights transfer request for an end user can be automatically originated by the service provider, for example based on the end user preferences indicated in the an service providers data base containing end user profiles regarding digital multimedia rights grants. 
     For example, the requesting or source end user may (by one of several methods, such as usage of a web portal) indicate to their service provider (as part of their service profile) to automatically transfer their digital multimedia rights to a given destination under certain circumstances such as presence information. 
     When a digital rights transfer request is received by the service provider, the service provider may wish to authenticate and validate the request with either or both the originating and destination users. Authentication may require the provision of a password or other ‘secret’ information as part of the digital multimedia rights transfer request. Validation involves confirming that the user has usage of the service. For example, if the service provider offers the service for a fee, and the user hasn&#39;t paid the fee, then the user may not be able to use the service unless they subscribe to the service or pay a fee. The fee could be recurring, or one time, or pay per use, etc. 
     A variety of methods may be used to enable the destination end user to whom the multimedia digital rights are being transferred to accept the transfer at an end user device with which the destination end user is associated. The acceptance of the transfer can occur on a first end user device associated with the destination end user to allow a transfer to a second end user device associated with the destination end user. These include the following a network originated (e.g. interactive voice responder (IVR)) call to the destination end user, announcing, e.g. ‘Joe has requested transfer of his television package rights to your television service. Please press 1 to accept the request, or 2 to deny the request, or 3 to speak to a service representative’. A network originated prompt to the destination user&#39;s television, e.g. ‘Joe has requested transfer of his television package rights to your television service. Please press Enter’ to accept the request, or ‘Cancel’ to deny the request. A pop up window on the destination user&#39;s PC, laptop, or netbook. This may be especially appropriate if the Transfer Request was originated from a device on the destination user&#39;s home network (e.g. the destination user&#39;s PC). The destination party may need to provide security information prior to accepting the transfer request. 
     Within an internet protocol television (IPTV) domain, every household has a set of grants, rights that give it packages. An Application Server (AS) can query what subscribers&#39; rights are, and can set them. Therefore a Video Application Server can: Receive a request for digital multimedia rights transfer from a source end user. Authenticate the source end user to determine that the source end user is indeed who they say they are; Validate the request to confirm that the source end user has the rights they are requesting to transfer, for example, their account is currently paid and not in arrears; Query the source end user end user or subscriber&#39;s service profile to ensure they have the service; Query the originating source end user/subscriber&#39;s grants to ensure they have the rights they are requesting to transfer. Determine if the source end user wants to transfer all or subset of their grants. Query and store the destination subscriber&#39;s digital rights grants (for later restoring or current merging of the destination end user&#39;s digital multimedia rights with the source end user&#39;s transferred grants of digital multi-media rights). 
     In a particular illustrative embodiment, the originating end user digital multimedia rights transferred grants are added to or merged with the destination end user digital multimedia rights grants. Upon cancellation, an illustrative embodiment restores the destination end user subscriber&#39;s grants as they originally were and restored the source end user&#39;s rights as they existed before the transfer. All rights transferred from the source end user are temporarily suspended at the source end user until the transfer is terminated. In another illustrative embodiment, a source end user can pay for an extension or digital multimedia rights so that the source end user can transfer some or all of their digital multimedia rights which paying to maintain the transferred digital multimedia rights at the source end user&#39;s end user device. 
     When the digital rights transfer request is received by the IPTV video application server, the application server may determine the difference between the originating user&#39;s service set of digital multimedia rights, and the destination user&#39;s service set of digital multimedia rights; and add the difference to the destination user&#39;s service set. An illustrative embodiment also offers the originating user a selection of which services should be transferred. Note that with this approach, the originating source end user&#39;s digital multimedia rights don&#39;t simply overwrite the destination end user&#39;s digital multimedia rights. For example, if a pay for view movie is ordered at the destination user&#39;s home after the visitor&#39;s rights transfer has taken place, the destination user is still the responsible billing party. Additionally, the destination user doesn&#39;t lose any of the rights they had. The resultant set of rights is a merger of the destination user&#39;s rights plus additional rights from the originating user. As a simpler alternative, the originating user&#39;s digital rights may overwrite the destination user&#39;s rights. However this approach may result in the destination user being deprived of rights they would like to retain, and as such be less attractive than an approach that merges all or part of the originating user&#39;s rights with the destination party&#39;s rights. However, with the over writing approach the originating user could be responsible for any additional, e.g. pay per view, charges incurred. 
     The digital multimedia rights transfer can be manually cancelled using the same or similar methods as those used to request the transfer, or may automatically cancelled, for example as a function of the end user&#39;s end user device location. For example: When Joe leaves Bob&#39;s house, Joe&#39;s cell phone de-registers from Bob&#39;s femtocell and registers with a macro cell or cell tower provided by Joe&#39;s cell phone carrier. The de-registration can be detected in the cell phone, reported, and terminate the digital multimedia rights transfer. The de-registration can be detected in the femtocell, reported, terminate the digital multimedia rights transfer. The macro cell registration can be detected in the IPTV system, reported, and used to initiate termination of the digital multimedia rights transfer. The digital multimedia rights transfer could also be cancelled as a function of duration expiration. For example, duration could be expressed in the transfer request, and when that amount of time is over, the transfer is cancelled. As an option, when the transfer is cancelled, the originating party could be queried to determine if they would like to extend the duration of the transfer. If unacknowledged, the transfer would be cancelled. 
       FIG.  2    provides an exemplary functional message flow between components of a system for enabling multimedia digital rights transfer. FIG,  2  depicts messages and data transferred between a source end user device  118 , an access network  110 , a digital rights transfer server  108 , an end user profile data base  134  an destination end user device. The previously identified service examples provide instances of video streaming based on content from a service provider. However it may also be possible to stream content from the user&#39;s DVR (for which the user owns digital rights) to a remote terminal. Here is an example of an illustrative use case as an extension of the previously provided scenario where Kathy visits her mother, and her digital rights automatically follow her: Kathy visits her mother every Saturday afternoon from approximately noon until 3 PM.—They both love the Mother Nature show that Kathy subscribes to, but her mother doesn&#39;t. Kathy has a illustrative embodiment of the system, method and computer program product described herein, which is also referred to herein as “the Follow Me service” from her service provider. She uses her service provider&#39;s friendly web portal to have her television package transferred to her mother&#39;s house whenever she is there. Her mother agrees to this. On Saturday, Kathy arrives at her mother&#39;s house. Kathy&#39;s cell phone location is known to the service provider (e.g. by its registration on her mother&#39;s femtocell, or by base station triangulation, or by GPS coordinates, or other means), and reported to the video application server (e.g. a ‘watcher’ of Kathy&#39;s location). Kathy&#39;s multimedia digital rights are automatically transferred to her mother&#39;s house. Kathy and her mother start to watch the current Mother Nature show, but her mother missed the previous show and would like to watch it. Kathy has it recorded on her U-Verse DVR back at her home. Kathy can have the content on her U-Verse DVR (to which she owns digital rights) streamed not to her TV, but to her Mother&#39;s TV. 
     Kathy and her mother watch the previous Mother Nature show, streamed from Kathy&#39;s home DVR. Kathy goes back home. When Kathy leaves her Mother&#39;s home, the content from her home DVR can no longer be streamed to her Mother&#39;s home. 
       FIG.  3    is a diagrammatic representation of a machine in the form of a computer system  300  within which a set of instructions, when executed, may cause the machine to perform any one or more of the methodologies discussed herein. In some embodiments, the machine operates as a standalone device. In some embodiments, the machine may be connected (e.g., using a network) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client user machine in server-client user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. 
     It will be understood that a device of the present invention includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. 
     The computer system  300  may include a processor  302  (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory  304  and a static memory  306 , which communicate with each other via a bus  308 . The computer system  300  may further include a video display unit  310  (e.g., liquid crystals display (LCD), a flat panel, a solid state display, or a cathode ray tube (CRT)). The computer system  300  may include an input device  312  (e.g., a keyboard), a cursor control device  314  (e.g., a mouse), a disk drive unit  316 , a signal generation device  318  (e.g., a speaker or remote control) and a network interface. 
     The disk drive unit  316  may include a machine-readable medium  322  on which is stored one or more sets of instructions (e.g., software  324 ) embodying any one or more of the methodologies or functions described herein, including those methods illustrated in herein above. The instructions  324  may also reside, completely or at least partially, within the main memory  304 , the static memory  306 , and/or within the processor  302  during execution thereof by the computer system  300 . The main memory  304  and the processor  302  also may constitute machine-readable media. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations. 
     In accordance with various embodiments of the present invention, the methods described herein are intended for operation as software programs running on a computer processor. Furthermore, software implementations can include, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein. 
     The present invention contemplates a machine readable medium containing instructions  324 , or that which receives and executes instructions  324  from a propagated signal so that a device connected to a network environment  326  can send or receive voice, video or data, and to communicate over the network  326  using the instructions  324 . The instructions  324  may further be transmitted or received over a network  326  via the network interface device  320 . The machine readable medium may also contain a data structure for containing data useful in providing a functional relationship between the data and a machine or computer in an illustrative embodiment of the disclosed system and method. 
     While the machine-readable medium  322  is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple tangible media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to: solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories; magneto-optical or optical medium such as a disk or tape; and/or a digital file attachment to e-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the invention is considered to include any one or more of a machine-readable medium or a distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored. 
     Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. Each of the standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, and HTTP) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents. 
     The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Other embodiments may be utilized and derived there from, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. 
     Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. 
     The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.