JP2016505932A - System and method for using network services in receiving content and data - Google Patents

Abstract

The first device implements a platform that is shared with the second device. The platform is implemented such that the first device and the second device operate with at least the same identification information for the network service. The first device provides a user interface to receive input for accessing or using the network service. The first device communicates received input in response to providing a user interface to the network service. The first device receives a token from the network service in response to communicating the input. The first device communicates the set of data items to the second device. The set of data items includes a token and an identifier that allow the second device to access and use the network service while appearing to the network service as the first device.

Description

  Embodiments described herein generally relate to systems and methods for presenting content, and more particularly to systems and methods for presenting content with time-based metadata.

  Network services (or sometimes referred to as “cloud” computing services) exist in various forms. For example, cloud music services, including PANDORA, SPOTIFY, and RHAPSODY, are available to users on various computing platforms. More generally, various network services are available to users, such as video streaming services, photo sharing sites, social networking sites, and game sites. Many types of devices are used to access these services. For example, it is common for network services to be accessible to mobile devices, tablets and personal computers running different types of applications or browsers.

A method for using network services using multiple devices
Implemented by one or more processors,
Implementing an application platform shared with a second device on a first device, wherein the application platform is configured such that the first device and the second device are at least for the network service. Implemented so that it can operate to have the same identification information, and
Providing a user interface on the first device to receive input to access or use the network service;
Communicating input received from the first device in response to providing the user interface, wherein the input is communicated to the network service; and
Receiving a token from the network service in response to communicating the input;
Communicating a set of data items to the second device, wherein the set of data items is such that the second device appears to the network service as the first device; Communicating, including the token and one or more identifiers that allow a network service to be accessed and used.

FIG. 2 illustrates an example system in which multiple devices cooperate with each other when accessing a network service of network service data items. FIG. 3 illustrates a logical architecture for a playback device, according to one or more embodiments. FIG. 6 illustrates a method for operating a computing device to process user interface operations for network services separately from a device provided with playback capability, in accordance with one or more embodiments. FIG. 6 illustrates a method for operating a playback device to output content from a network service separately from a device provided with a user interface function for the network service according to one or more embodiments. . FIG. 6 illustrates a method for handling user interface events generated from a network service when multiple devices access the network service simultaneously. FIG. 2 illustrates an exemplary method for implementing a digital rights management (DRM) scheme in the context of two devices accessing a network service. FIG. 6 illustrates a method for operating a network service to allow a user to access the network service using multiple devices, according to one or more embodiments. FIG. 1 illustrates a system for implementing a rights management service in the context of a user interface and playback device, in accordance with one or more embodiments. FIG. 2 illustrates an architecture for a rights management service, according to one embodiment. FIG. 6 illustrates a method for utilizing a rights management service in accordance with one or more embodiments. FIG. 3 illustrates a user interface device according to one or more embodiments. FIG. 6 illustrates a playback device, according to one or more embodiments.

  The embodiments described herein provide a computing environment in which the use of network services can be distributed among multiple devices. In particular, the examples described herein provide a search or playback device that communicates with a network service to receive data items (eg, content). During the same session, another device can communicate with the network service to handle user interface events and functions on behalf of the search or playback device. Such a configuration allows for a greater diversity of types of devices that can be used for retrieval or playback of data items from network services. For example, a device or dedicated player can operate to retrieve content from a network service without the device needing to be able to use direct user interaction. Rather, user interaction that might otherwise be required from equipment or a dedicated player may be provided through another device.

  Further, some embodiments use an intermediate rights management service that can operate to communicate rights management rules that control how a search or playback device accesses and uses a given network service. I will provide a. The rights management service may be used to allow independent applications or non-platform specific applications to be used in connection with search or playback operations from any one of a plurality of network services. Among the benefits, rights management services allow access to and use of network services without the need for proprietary or specific client applications that implement rights management rules for specific network services.

  In some embodiments, the network service is utilized by multiple devices. In one embodiment, the first device implements an application platform that is shared with the second device. The application platform may be implemented to operate such that the first device and the second device have the same identification information for at least the network service. The first device provides a user interface to receive input for accessing or using the network service. Further, the first device communicates received input in response to providing a user interface to the network service. The first device may receive a token from the network service in response to communicating the input. Further, the first device can communicate a set of data items to the second device. The set of data items is a token and one or more identifiers that allow the second device to access and use the network service while appearing to the network service as the first device Including.

  In another variation, the playback device implements an application platform that is shared with the user interface device. The application platform may be implemented such that the playback device and the user interface device can operate to have at least the same identification information for the network service. The playback device communicates with the user interface device to receive the set of data items, the set of data items accessing (i) the token communicated to the user interface device by the network service, and (ii) accessing the network service. And one or more identifiers used by the user interface device. The playback device accesses the network service using the token and one or more identifiers received from the user interface device.

  According to some embodiments, the universal search or playback component allows the computing device to access any one of a plurality of possible network services according to the rights management rules of the intermediate rights management service. Can be used with that service to make it available.

  Among the benefits, the embodiments described herein provide various types of network services (e.g., cloud media services, photo sharing sites, etc.) and a wide range of devices (Internet-enabled accessories or equipment devices that stream content). ) Allows you to receive and use on. In particular, the device can utilize such services without the device needing to be able to use user interaction. Further, some embodiments provide such devices that use universal programs or resources to access network services, and thus such devices are resident to implement functionality such as rights management rules. There is no need to have proprietary (or previously installed) proprietary or service-specific applications.

  Some embodiments described herein provide systems, methods and devices for utilizing network services. In one embodiment, the first device is operable to provide a user interface for network services. Input received from the first device in response to providing the user interface is communicated to the network service. In response to communicating the input, the user interface device receives a token for accessing the network service. The user interface device communicates the token to the playback device.

  According to another embodiment, the playback device operates to receive multiple links from the user interface device. The multiple links can identify (or can be used to identify) one or more network service data items. The network service data item identified by each of the plurality of links is retrieved from the network service. While the network service data item is retrieved, the playback device detects the occurrence of a user interface event generated from the network service. Data identifying the user interface event is communicated to the user interface device.

  Still further, embodiments include a system that includes a first device and a second device. The first device provides a user interface and the second device includes a data output component. The first device may be configured to receive information from the user through the user interface and communicate the information to a network service. The first device may also receive a token or other programmatic proof from the network service in response to communicating the information. The first device may communicate the token to the second device. The second device may be configured to use the token to access network services without receiving input from the user. Data items received from the network service are output using the output component.

  Still further, embodiments provide a playback device that operates to receive a plurality of links from a user interface device. Each of the plurality of links identifies one or more network service data items. A network service data item is identified and retrieved by each of the plurality of links. While searching for network service data items identified by each of the plurality of links, the occurrence of a user interface event is detected using the network service. Data identifying the user interface event is communicated to the user interface device.

  In another embodiment, the network service is utilized on the playback device. On the first device, a session with a network service is established to receive media data items for playback. With the first device, the second device is controlled to access the network service during the session and use the first device's programmatic credentials to retrieve the media data item.

  In another embodiment, a computer system for utilizing network services is provided. The computer system includes a memory for storing a plurality of network service libraries, where each network service library is associated with a corresponding network service. Each network service library includes (i) a set of link data, where the link data identifies data items provided on the network service, and (ii) rights management for the network service. And a set of rules. The processor of the computer system can determine the network service specified by communication. The processor can also determine link data in the set of link data that identifies each identifier in the set of identifiers from the network service library. One or more control parameters for communication based on a set of rights management rules for the determined service are also determined. The set of links is communicated to the playback device based on the determined link data. The set of links may also be communicated along with control parameters to allow the playback device to retrieve data items from the determined network service according to the set of rights management rules for that network service.

  In one embodiment, a first set of links is received from a user interface device. Each link in the first set of links (i) identifies a data item on the corresponding first network service and (ii) directs the playback device to an intermediate network service. A first set of links is signaled to the intermediate network service, and in response, a second set of links is received from the intermediate network service. Each link in the second set of links identifies one data item of the set of identifiers.

  According to another embodiment, the first set of links is such that each link in the first set of links identifies (i) a corresponding data item on the first network service, and (ii) an intermediate Built to link to network services. The first set of links is signaled to the playback device to cause the playback device to access intermediate network services.

  Still further, embodiments provide a player capable of playing content from multiple network services on a computing device. Network services can detect and use players as an alternative to service specific applications for that service. Media resources from a network service may be played by accessing an intermediate rights management service to identify a set of media resources from the network service for playback. A set of playback links for each media resource in the set is received from the intermediate rights management service. Each set of playback links links to a corresponding media resource provided by the network service.

  One or more embodiments described herein provide that the methods, techniques, and actions performed by a computing device are performed programmatically or as a computer-implemented method. Programmatic means using code or computer-executable instructions. The steps performed programmatically may or may not be automatic.

  One or more embodiments described herein may be implemented using programmatic modules or components. Programmatic modules or components may include programs, subroutines, portions of programs, or software or hardware components that are capable of performing one or more of the above tasks or functions. As used herein, a module or component can reside on a hardware component independently of other modules or components. Alternatively, the module or component may be a shared element or process of another module, program or machine.

  Further, one or more embodiments described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions can be carried on a computer-readable recording medium. The machines illustrated in the following figures or described in the following figures provide examples of processing resources and computer-readable recording media on which instructions for implementing embodiments of the present invention may be carried and / or executed. In particular, a number of machines shown with embodiments of the present invention include a processor and various forms of memory for holding data and instructions. An example of a computer-readable recording medium is a permanent memory storage device such as a personal computer or a hard drive on a server. Other examples of computer storage media include portable storage units such as CD or DVD units, flash memory (eg, carried on many multifunctional phones and portable computing devices), and magnetic memory. Computers, terminals, network-enabled devices (eg, mobile devices such as cell phones) are all examples of machines and devices that utilize instructions stored on a processor, memory, and computer-readable storage media. Further, the embodiments may be implemented in the form of a computer program or a computer usable carrier medium capable of carrying such a program.

  System overview

  FIG. 1 illustrates an exemplary system in which multiple devices cooperate with each other when accessing network services. In particular, the exemplary system 100 accesses and uses the network service 102 through a first device provided as the user interface device 110 in FIG. 1 and a second device provided as the playback device 120 in FIG. It becomes possible to do. Network service 102 may be accessed over network 113 (eg, the Internet) by each of user interface device 110 and playback device 120 through a website, for example. Network services 102 that may be used by exemplary system 100 include, for example, websites (eg, social networking sites, photo sharing sites, etc.) or cloud-based media services (eg, music playback sites such as PANDORA).

  Among the benefits, the example in Figure 1 recognizes that there are many types of network-enabled devices, but some network-enabled devices are not suitable for handling user interface interactions required from the network service 102. To do. For example, some devices, such as televisions, require the use of remote controls that are difficult for the user to operate to provide input. Other devices, such as streaming or restreaming equipment, have limited or no user interaction capability that is local on the device. Such operating environments limit the ability of these devices to use such services, particularly when network services require user interaction for some events.

Referring to the example of FIG. 1, system 100 includes a user interface device 110 and a playback device 120. The user interface device 110 can correspond to any network enabled computing device that can receive user input and communicate such input to other devices and / or network services or websites. By way of example, user interface device 110 may correspond to a mobile computing device (e.g., a multifunctional cellular / phone device such as a smartphone), a tablet, a laptop, a netbook, an integrated computing device, a personal computer, etc. . The user interface device 110 includes a network service interface 112, a user interface 114, and a device network interface 116. A component may be implemented using a combination of hardware, logic and / or software. The network service interface 112 may be associated with providing resources for the network service 102, or in some cases may include software or logic to access a network location or site used in providing it. . Network service interface 112 uses logic (e.g., a wireless port such as cellular, wireless fidelity ("Wi-Fi"), or Bluetooth) on user interface device 110 (e.g., Client applications such as commercial browsers or web-based applications). User interface 114 may include a combination of input and / or output components such as a touch screen display, a microphone (with corresponding voice recognition), a keyboard or other button input mechanism, or other type of user interface mechanism. it can. The device network interface 116 may include logic (eg, applications) that utilize the same or different network ports to communicate with at least the playback device 120. In some implementations, the device network interface 116 may include logic (eg, software, firmware) to allow the device to be a member of a personal network.

  In the example of FIG. 1, the playback device 120 can include a network service interface 122, an output component 124, and a device network interface 126. As an example, the playback device 120 can correspond to a device for accessing cloud services, network resources, and the like. For example, the playback device 120 can correspond to a streaming output device, a television, or an Internet device. In some variations, the playback device 120 is another computing device that has user interface capabilities but is used in conjunction with the user interface device 110 to access the network service 102 according to user preferences or designations. obtain. Thus, the playback device 120 can correspond to a mobile computing device (eg, a multifunctional cellular / phone device such as a smartphone), a tablet, a laptop, a netbook, an integrated computing device, a personal computer, and the like. The network service interface 122 includes logic for utilizing a network port (eg, a wireless port such as cellular, Wi-Fi, or Bluetooth) on the playback device 120.

  The output component 124 generates playback data 125 that can be output as audio and / or video. In one implementation, playback device 120 includes an output device, such as a speaker and / or display screen, to provide output from playback data 125. In another implementation, playback device 120 communicates playback data 125 in some form to another connected device. For example, the playback device 120 can signal analog and / or digital data corresponding to the playback data 125 to the connected device. In a variant, the playback device 120 may further process the playback data 125, for example, by transcoding the playback data 125 to another format. Still further, playback device 120 provides services or components for outputting content based on playback data 125 and / or processing playback data 125 (eg, transcoding playback data 125 on another device). (Eg, network connection components) can be utilized.

  The device network interface 126 of the playback device 120 can include logic (eg, applications) that utilize the same or different network ports to communicate with at least the user interface device 110. In some implementations, the device network interface 116 may include logic (eg, software, firmware) to allow the device to communicate with the user interface device 110.

  The user interface device 110 and the playback device 120 can communicate with each other via the network link 111. The network link 111 may correspond to, for example, a local network link, and more specifically, a wireless local link (eg, a Wi-Fi or Bluetooth® link). In a variant, the network link 111 may utilize a cellular network and / or a wide area network such as the Internet.

  In some implementations, each of the user interface device 110 and the playback device 120 is a U.S. Patent Application No. 10 / 808,606, which is hereby incorporated by reference in its entirety for all purposes. Can operate as a satellite on a personal network. In such an implementation, each of the user interface device 110 and the playback device 120 is an application or other programming that allows the device to communicate its capabilities and connection status to the registry of a particular personal network device. Logic can be used. The registry may be centralized on one device (eg, a personal computer), distributed over multiple devices in a personal network, or provided as a network service. In one implementation, each of the user interface device 110 and the playback device 120 includes a personal network registry 118, 128 that allows the device to act as a member (or satellite) of the user's personal network, respectively. When implemented as a personal network, some of the communications and functions described as being between the user interface device 110 and the playback device 120 may be automatically initiated or executed in response to a number of conditions. For example, user actions of the user interface device 110 can communicate with the network service 102 and trigger the playback device 120 to utilize it in the manner described below using various embodiments. Similarly, another implementation may provide for the use of playback device 120 to automatically initiate operations such as those described below on user interface device 110.

  In some embodiments, the user interface device 110 operates to gain access to the network service 102. For example, the user can launch a shortcut or application launch on the user interface device 110. In response, an application running on the user interface device 110 generates user interface features to prompt the user to provide input that may be needed or otherwise utilized with the network service 102. Input provided by the user may be used to access the network service 102. In one limitation, user interface device 110 communicates user input 107 to network service 102 via network service interface 112. User input 107 may correspond to, for example, login and password information or other account / identification information to allow network service 102 to determine the user's account or settings. In response, the network service 102 can issue an authorization token 131 to the user interface device 110. The authorization token 131 can correspond to a data item issued by the secure network site to identify and / or authenticate the user. The network service interface 112 may communicate the authorization token to the device network interface 116, which in turn communicates the authorization token 131 to the playback device 120. In one implementation, the user interface 114 of the user interface device 110 and the output component 124 of the playback device 120 communicate the authorization token 131 from the user interface device 110 to the playback device 120 and then use it on the playback device 120. Part of a common application or application platform that enables

  In addition to obtaining and signaling the authorization token 131, the user interface device 110 may specify a selection input 109 for selection of a particular network service data item 106 for selection or retrieval by the playback device 120. Can be used. For example, the user interface device 110 may be used to search, navigate, browse, or identify data items for selection or retrieval from the network service 102. In response to receiving selection input 109, network service 102 may provide a link 105 to enable retrieval of the selected network service data item. In a variation, the network service 102 may be triggered to automatically identify network service data items for the user or device. Still further, in other variations, the selection input 109 may be sent from the playback device 120. For example, playback device 120 may store selection input 109 (eg, a favorite playlist, etc.) or receive selection input 109 from user interface device 110.

  The playback device 120 receives the authorization token 131 from the user interface device 110. In one implementation, the device network interface 126 of the playback device 120 receives the authorization token 131 from the user interface device 110 and then communicates the token to the network service 102 via the network service interface 122. In addition to signaling the authorization token 131, the playback device 120 may signal the link 105 for the selected data item. For example, the playback device 120 can signal a link 105 to a network service that identifies media files (eg, music, video). The link 105 identifies the network service data item 106 that the network service 102 communicates with the playback device 120. The output component 124 generates playback data 125 corresponding to the network service data item 106.

  In some implementations, the playback device 120 is triggered by the user interface device 110 to automatically access the network service 102 using the authorization token 131 and the link 105. For example, the user interface device 110 can trigger the playback device 120 to access a data item from the network service 102 by signaling an authorization token 131.

  Playback device

  FIG. 2 illustrates a logical architecture for a playback device according to one or more embodiments. In one embodiment, the playback device 120 includes a device network interface 210, a search component 230, and an output component 240. In one embodiment, playback device 120 is programmatically configured to communicate data items and retrieve data items from a variety of different network services. For example, the playback device 120 may be configured to use a link to identify a data item from a network service and then trigger an operation in which the selected data item is streamed from the network service to the playback device 120. . As another example, playback device 120 may be configured to use a link to download a document or file identified by the link.

  The playback device 120 includes service logic 224 that may include an instruction set and / or configuration data for individual network services. In one implementation, the service logic 224 can include plug-ins or program files. In addition, the service logic 224 can include resources for network services, including a network service library 227 and a digital rights management (DRM) library 229. The network service library 227 can store, for example, a link 205 for use in retrieving network service data items from the corresponding network service 202. The DRM library 229 may be provided from a corresponding network service, for example, to control the playback or use of media resources from the network service 202.

  Device network interface 210 includes components for communicating with other devices of the user, such as user interface device 110 (see FIG. 1). In one implementation, device network interface 210 includes inbound components corresponding to token handler 212 and link analysis 214. The token handler 212 receives the token 131 (see FIG. 1) from the user interface device 110 and communicates the token to service logic 224 for accessing the appropriate network service. Link analysis 214 can operate to detect properties of link 205 received from user interface device 110, for example. For example, the link analysis 214 can determine a particular network service 202 to be utilized with a particular link. In some variations, as described below, the link analysis 214 should also utilize the rights management service 201 in connection with retrieving the corresponding network service data item from the corresponding network service 202. Can be used to determine if there is. Both authorization token 131 and replay link 205 may be communicated to service logic 224 to allow search component 230 to access and retrieve data items from a particular network service 102.

  In some embodiments, the search component 230 uses the authorization token 131 to access a set of data items 209 from the corresponding network service 202. Search component 230 uses authorization token 131 and one or more playback links 205 to search data item 209. The playback link 205 may be stored as part of a particular network service library 227, communicated from the user interface device 110, received from the network service 202, or from an intermediate service (as described below). The search component 230 may sequentially sequence the playback links 205 based on, for example, control rules specified in the DRM library 229 or, for example, control rules communicated from the user interface device 110, or Can communicate.

  Search component 230 can be controlled by control parameter 207 in a manner in which link 205 can be used. For example, the timing or sequence of how the link 205 is searched may be controlled by the control parameter 207. Control parameters 207 may be identified by service logic 224 used in retrieving media resources from network service 202. For example, the control parameter 207 may be identified or determined from the DRM library 229 that is used with or associated with a particular network service.

  Search component 230 uses playback link 205 to search for data item 209 from network service 202. In one implementation, data corresponding to the retrieved network service data item 206 is signaled to the output component 240. The output component 240 can generate output content or playback on the playback device 120. In a variant, the data 206 corresponding to the retrieved network service data item 206 is signaled to the device network interface 210 for processing or communication. For example, data 206 may be (i) another device connected or linked to playback device 120, (ii) another element of the same personal network for output, or (iii) service (e.g., transcoding) Can be signaled to another element of the same personal network. Still further, the data 206 can be stored on the playback device 120 for later use.

  Embodiments recognize that many network services include events that trigger the need for user interaction, and the ability for users to respond to events may be required to avoid disrupting service availability. . For example, the network service may prompt the user for login and password information intermittently or ask the user a question (eg, ask the user to rate the service). In some embodiments, the search component 230 includes a user interface event detection component 232. When a particular network service encounters a user interface event, UI event detection component 232 signals a UI trigger 239 that initiates the rendering of the UI event on user interface device 110. In one implementation, the UI trigger 239 is received by the outbound component 216 of the device network interface 210, which then signals a UI event 217 to the user interface device 110.

  In some embodiments, the device network interface 210 also operates to allow the playback device 120 to act as an element or satellite on the user's personal network. The device network interface 210 may include a device register 225 that identifies other elements (programs, devices, data sources, accounts, etc.) of the user's personal network. In particular, the device register 225 includes (i) the status of other elements of the personal network (e.g., whether other elements are active), (ii) related capabilities that may be utilized by the playback device 120 (e.g., transcoding ), And (iii) data identifying network locations of other elements of the personal network. In this way, the device network interface 210 can signal data 206 to other elements of the personal network and / or utilize personal network resources in processing the data 206.

  Rights management search on playback devices

  In some embodiments, the playback device 120 can utilize the intermediate rights management service 201. With further reference to FIG. 2, the intermediate rights management service 201 can provide a service that allows the rights management control of different network services 202 to be implemented as separate network services. For example, the use of web services to implement rights management for network services provides an alternative to traditional approaches, where each network service 202 needs to implement rights management controls as part of the client application. There is. Among the benefits, some embodiments allow the use of an intermediate rights management service 201 to eliminate or reduce the need to maintain service-specific programmatic or data resources on the playback device 120.

  On the playback device 120, the device network interface 210 receives a control link 211 that directs the rights management search component 220 to the rights management service 201. Rights management search component 220 uses control link 211 to access rights management service 201. The rights management service 201 identifies the control parameters 223 of the network service 202 that are to be used by a particular set of control links 211. As described in other examples, rights management service 201 may be used to handle rights management for multiple network services (eg, PANDORA, SPOTIFY, etc.). In one implementation, the rights management service 201 signals the playback link 205 to the playback device 120 along with control parameters 223 that are specific to the network service 202 identified on the control link 211. Replay link 205 and control parameters 223 are used by search component 230 to search for data items 209 from a particular network service 202.

  Method

  FIG. 3A illustrates a method for operating a computing device to process user interface operations for network services separately from a device provided with playback capabilities. FIG. 3B shows a method for operating a playback device to output content from a network service separately from a device provided with a user interface function for the network service. FIG. 3C illustrates an exemplary method for handling user interface events when the user interface and playback functions are handled by different devices, according to one or more embodiments. FIG. 3D shows an exemplary method for implementing a digital rights management (DRM) scheme in the context of two devices accessing network services. FIG. 3E illustrates a method for operating a network service to allow a user to access the network service using multiple devices. In describing the exemplary method of FIGS. 3A-3E, the elements described in FIG. 1 or FIG. 2 are used to describe suitable components or elements for performing the described steps or substeps Reference may be made to components.

  Referring to FIG. 3A, the user interface device 110 implements an application platform (308). In one implementation, the application platform provides a user interface device to access a particular network service, or possibly to an application or application service that allows the user interface device to access a particular network service. Correspond. An application platform can be an application platform that is specific to a device type and platform (eg, an operating system) while being shared with another device and device platform (eg, playback device 120).

  User interface device 110 operates to display user interface functions for interacting with network services (310). In one implementation, user interface functions may be proprietary or specific to a particular network service. For example, clients and web-based applications can be installed, proprietary, or specific to a particular network service. In a variant, the user interface functionality may be provided in the form of an application that is general or not specific to different network services. For example, the application can prompt the user for input such as login and password, specification of a particular network service that the user wishes to use, and other input such as search or navigation input to select data items. . Still further, the user interface functionality may be provided as a browser or similar application running on the user interface device 110. For example, a browser can load an application from a network site and provide network services through the application executing the browser.

  User interface device 110 may operate to communicate user input to a selected network service (320). In particular, the input can include information for identifying an account associated with the user. The input can also include information for an authorized user to access the account, for example, the information can include a login or password or other identifier (eg, machine identifier, cookie, etc.). Optionally, the input can also be in the form of a selection input such as search, navigation, etc.

  The user interface device 110 receives a token from the network service (330). In one implementation, the token may be session specific and allow the user to use the user interface device 110 to authorize access to the user's account and network services. In granting permission, the network service may also identify the user interface device 110. For example, the network service may identify the user interface device 110 by one or more selection parameters, including as a cookie stored on the user interface device or as a machine identifier for the user interface device 110.

  User interface device 110 may communicate a set of data items to playback device 120 (340). The set of data items can include a token (342). In some variations, the set of data items includes one or more identifiers used by the network service to identify the user interface device 110 (344). Since the user interface device 110 and the playback device 120 share a common application platform, a set of data items communicated from the user interface device 110 may cause a receiving device (eg, the playback device 120) to access a network service. It may be possible to look like a user interface device. In a variant, the set of data items includes a token, but other identifiers are obtained by the playback device 120 in a previous exchange with the user interface device 110. For example, the playback device 120 can receive the application platform (or a portion thereof) from the user interface device 110 during a previous exchange, and the identifier communicated as part of the application platform determines the identifier of the network service Can be used for.

  Under conventional techniques, tokens received from network services are often valid for the receiving device for a particular session. The network service pairs subsequent uses of the token with, for example, an identifier associated with the application that accesses the service. In the example of FIGS. 1 and 2, the user interface device 110 and the playback device 120 share a copy of the same application and its identifier (eg, cookie). In this way, the playback device 120 can access a particular network service using the identifier communicated to the user interface device 110.

  In some embodiments, the user interface device 110 also communicates 350 a link that the playback device 120 can use to access data items from network services. For example, the user may perform a search operation to select a data item using the user interface function of the user interface device 110. In some embodiments, a link may directly identify a data item on a particular network service. In other embodiments, such as the embodiments described in FIGS. 4-6, the link communicated from the user interface device 110 identifies an intermediate rights management service, which is a control parameter for a particular network service. And change the link to use that network service along with rights management rules and communicate different links.

  Referring to FIG. 3B, the playback device 120 implements an application platform shared with the UI device 110 (358). In one implementation, the application platform provides a playback device 120 to access a specific network service, or possibly an application or application service that allows the playback device 120 to access a specific network service. Correspond. The application platform may be specific to the device type and platform (eg, operating system) of the playback device 120. In one variation, the playback device 120 receives at least a portion of the application platform from the UI device 110.

  Still further, in some variations, playback device 120 may receive data items from user interface device 110 (360). The data item received from the UI device 110 includes a token received from the network service as well as one or more identifiers that allow the playback device 120 to look like the UI device 110 when accessing the network service. Can do. By way of example, the identifier may include a cookie initially stored on the UI device 110 (eg, received when the UI device 110 has accessed network services), or a machine identifier of the UI device. Further, identifier communication may also be carried through a shared application platform, which may include functionality for making playback device 120 appear to UI device 110 to an external source.

  In one embodiment, playback device 120 may execute an application that is an instance of a network service interface used to access network services on user interface device 110. For example, the playback device 120 executes an instance of a web-based client application for a particular network service so that the token received from the user interface device 110 allows the playback device 120 to access the network service. obtain.

  In some embodiments, playback device 120 may receive playback link 205 from user interface device 110 (364). The playback link 205 can specify the location of a specific data item from a specific network service. Accordingly, playback device 120 uses playback link 205 to receive data items from the network service (368). For example, the playback link 205 may be used to locate a media file, such as a song, video or other media content. Once located, the network service can stream data corresponding to the selected item to the playback device 120. In a variant, the search can identify files or documents that can be transferred to the playback device 120.

  The playback device 120 can output data or content corresponding to the retrieved data item (372). In one implementation, the playback device 120 outputs content corresponding to the retrieved data item on the device. In a variation, playback device 120 has limited output capability, but rather it streams content data (e.g., in analog form to other output devices such as traditional non-network television or stereo). Or a dedicated device for signaling (374). In one variation, the playback device 120 may stream data to the target device using, for example, a wireless (or wireline) connection. Additionally or alternatively, playback device 120 may utilize a personal network device or resource to output or communicate data corresponding to the retrieved data item (376). For example, playback device 120 can transcode data items retrieved using a chance coating resource or application on a personal network into an alternative format. As another example, playback device 120 can stream data corresponding to retrieved data items to a target device on a personal network while simultaneously receiving a stream corresponding to the data items from a network service.

  FIG. 3C illustrates a method for handling user interface events generated from a network service when multiple devices access the network service simultaneously. More specifically, referring to FIG. 3C, embodiments recognize that network services often generate user interface events, sometimes even after a session has begun. In such user interface events, user input may need to avoid interruptions or maintain full availability of the service. According to one embodiment, the playback device may include logic to detect when such a user interface event occurs when accessing a network site (380). For example, user interface events can include mandatory events such as prompts that require the user to exist or perform some action such as having the user re-enter credentials. In other network services, it may be necessary to display advertisements so that each advertisement corresponds to a user interface event. Still further, the type of user interface event may include input that a user may provide to improve the service. For example, a user may wish to signal feedback indicating a user's likes or dislikes for a particular data item. In the media context, for example, user feedback may be used in selecting additional data items for the user. Thus, although user feedback is not always necessary, the user may wish to provide input to fully realize the benefits of network services.

  In conjunction with the occurrence of a user interface event, one or more embodiments provide that playback device 120 signals to user interface device 110 regarding the occurrence of the user interface event (382). In one implementation, the playback device 120 can signal to the user interface device 110 that an event has occurred, and the network service interface 112 of the user interface device 110 allows the user to provide feedback or response to the event. The network service 102 can be accessed (384) to obtain user interface information and functions for In another implementation, the playback device 120 can retrieve a user interface function and signal it to the user interface device 110 where it is presented to the user.

  FIG. 3D shows an exemplary method for implementing a digital rights management (DRM) scheme in the context of two devices accessing network services. In one embodiment, UI device 110 and playback device 120 exchange public keys (385). The UI device 110 then accesses the network service and logs in on behalf of the user (386).

  After logging in, the UI device may receive a link from the network service (388). The link may be for a desired song, playlist or channel. The UI device 110 encrypts the link using the public key (390), and sends the encrypted link to the playback device (391). Further, user interface device 110 may operate to communicate user input to network services. As an example, the input may be in the form of a selection input such as search, navigation, etc. For example, the user may perform a search operation to select a data item using the user interface function of the user interface device 110. In some embodiments, a link may directly identify a data item on a particular network service.

  The playback device holds the secret key, extracts the link to the network service, and uses the secret key to communicate (392). In response to communicating the link, the playback device receives the playback link from the network service (394). The playback link can identify data that can be streamed from the network service to the playback device. For example, a playback link may be used to locate a media file such as a song, video or other media content. Once located, the network service can stream data corresponding to the selected item to the playback device 120. In a variant, the search can identify files or documents that can be transferred to the playback device 120.

  FIG. 3E illustrates a method for operating a network service to allow a user to access the network service using multiple devices, according to one or more embodiments. In one embodiment, the network service 102 includes one or more processors 393 that operate to receive user input corresponding to a set of user credentials (393). The set of user credentials can include a user login and password, or other identifier that the user can specify to access the network service and link the network service to the account.

  Network service 102 may identify a device used by the user to communicate a set of certificates (395). For example, the network service 102 may attempt to determine a machine identifier or cookie associated with the computing device to determine whether the device has been previously used to access the network service 102 using the same set of credentials. It can be.

  Once the device is identified, a determination may be made as to whether the device is the first device in time to access the same user account or use the same set of credentials (396). The first device in time corresponds to the device that the user first used to access the network service 102 (for example, the device that the user used to establish an account and / or perform an initial download) To do.

  If the device is the first device in time, access is granted (397). However, if the device is not the first device in time, an additional set of decisions may be performed to determine whether the conditions for authenticating that the identified device is a subsequent device are met ( 398). If the condition is met, the identified device is allowed access to the network service as a subsequent device (399). Otherwise, the device may be denied access to network services (400).

  The permissions granted to subsequent devices may be the same or different from the permissions granted to the first device in time. When subsequent devices are authenticated, some embodiments allow network services to allow access to both the first and subsequent devices in time (e.g., during the same network session) at the same time. provide. For example, referring to FIG. 1, UI device 110 corresponds to the first device in time that a user can use to establish an account or session (e.g., a user can enter login credentials). can do. The playback device 120 can support the following devices. The credentials provided by playback device 120 may be provided programmatically, for example, through the playback device application interface.

  By way of example, some embodiments provide a network service that utilizes conditions corresponding to the identified device being the next device. At the next device authorization, the user first connects to the network using the first device, and the first device is then authenticated to use a particular network service. The next device that accesses the network service and uses the user's login and password is then also authenticated. In this way, two devices can be authenticated for a given user. As specified in the implementation, additional next device authentication may also be performed on the third or fourth device (e.g., the next two using the network service to log in and use the user's credentials). One device can be authenticated).

  Additionally or alternatively, the conditions for authentication correspond to the identified device being used to access network services within a given duration from when the first device in time was used be able to.

  Intermediate rights management service

  Many network services utilize business rules and rights management rules in a way that they can be used. For example, an online music service can limit the number of times a user can skip a song when listening to a channel. Further, in the context of media services, service providers are generally limited to a specific library of licensed works. Under conventional approaches, these and other restrictions are typically implemented through the data organization of client applications that access network services. For example, a music service often implements its business rules and rights management rules through programmatic control of its corresponding client application. Thus, a user may sometimes install multiple applications for various network services that the user uses.

  FIG. 4 illustrates a system for implementing a rights management service in the context of a user interface and playback device, according to one or more embodiments. Some embodiments described herein allow users of universal applications on each of UI device 410 and playback device 420 to use with multiple network services. Each of UI device 410 and playback device 420 uses a universal application to access any of a plurality of possible network services, for example, instead of a separate, dedicated web-based application for each individual network service can do.

  In the example of FIG. 4, UI device 410 signals to playback device 420 when using intermediate rights management service 430 to access a selected one of multiple possible network services 402. More specifically, UI device 410 may be operated by a user to submit user input 403 and obtain token 413 from network service 402, for example. The user interface functionality of UI device 410 may be based in part on user interface data 411 received from network service 402. The token 413 can be communicated to the playback device 420. In one implementation, token 413 may be automatically communicated to playback device 420 in response to UI device 410 obtaining token 413 from network service 402.

  In some embodiments, UI device 410 may also operate to allow a user to provide selection input for data items of network service 402. For example, UI device 410 can receive data 411 that allows a user to select a data item. For example, the UI device 410 can receive search results, menus and suggestions from the network service 402. Certain data items may be selected on the UI device 410. The UI device 410 can include a program that translates or structures the selection into an intermediate rights management (IRM) link 415, which can be communicated from the UI device 410 to the playback device 420. For example, the UI device 410 may include logic that takes the title of the selection as well as the network service from which the selection was made and configures a link to an intermediate management service 430 that identifies both the selected title and the network service 402. .

  The playback device 420 receives the token 413 and the IRM link 415 set from the UI device 410. The playback device 420 uses the IRM link 415 when accessing the intermediate rights management service 430. The intermediate rights management service 430 includes logic for mapping the IRM link 415 to the replay link 425 or network service 402 data items. Intermediate rights management service 430 also includes logic that identifies control parameters 427 for a particular network service 402. The logic for determining the control parameter may also be based on a context that considers, for example, the user's past history or recent actions (eg, the number of times the user skipped a song). On playback device 420, control parameters 427 control how playback link 425 should be used.

  The playback device 420 uses the token 413 and the playback link 425 when accessing the network service 402. The action of playback device 420 when using playback link 425 may be controlled or determined by control parameter 427. For example, the control parameter 427 may include (i) a sequence in which the regeneration link 425 is used, (ii) an action that can be performed when the regeneration link is used, and (iii) when the regeneration link is used. Actions that can be performed after being determined can be controlled, or (iv) whether replay link 425 can still be used (eg, the user has exceeded the number of hours to use the network service).

  Universal player and intermediate services

  Under typical conventional approaches, network services utilize service-specific or proprietary client applications to allow users to access data items such as media content. Under such conventional approaches, the client application controls the way in which the network service is used, particularly with respect to the rights management of content provided by the network service.

  In contrast, one or more embodiments provide for the use of a universal player 460 that allows a computing device to operate in utilizing multiple network services through a single client application. Referring to FIG. 4, an embodiment is a programmatic configuration to be included with the network service 402 to allow the network service to detect the presence of the universal player 460 on the computing device (eg, playback device 420). Element 450 is provided. When the universal player 460 is detected, the network service 402 may implement an action to communicate with that player instead of the default (eg, proprietary) player for that service.

  In order to implement rights management rules, universal player 460 may be configured to take advantage of the use of intermediate rights management service 430. In one embodiment, the universal player 460 generates or structures a set of IRM links 415 from input that may be received on either the playback device 420 or the UI device. Each IRM link 415 may be structured to point to an intermediate rights management service 430. The IRM link 415 can identify specific media resources and network services. In one embodiment, universal player 460 signals IRM link 415 to intermediate rights management service 430 to obtain playback link 425 and control parameter 427. The control parameter 427 can implement a network service right management rule. Implementation of rights management rules can be performed, for example, in the manner described in FIGS. In this way, the universal player 460 can implement different rights management rules for different network services by communicating with the intermediate rights management service 430.

  In a variant, the universal player 460 can reside on the UI device 410 and the IRM link 415 can be signaled to the playback device 420, which then obtains the playback link 425 and control parameters 427. To do. In another variation, the universal player 460 can reside on the UI device 410, and the universal player 460 creates an IRM link 415 to obtain the playback link 425 (along with the control parameter 427), which Can be signaled to the intermediate rights management service 430. A playback link 425 and a control parameter 427 may be signaled to the playback device 420.

  FIG. 5 illustrates an architecture for a rights management service according to one embodiment. Rights management service 430 may be implemented on a website accessible to playback device 120, for example. In one embodiment, rights management service 430 includes a device interface 510, a link analysis component 520, and a collection of services for individual network services. For each network service, the rights management service 430 includes a service library 530 and a set of service rules 532. Each service library 530 can include link data 531 that correlates an identifier specified from an incoming request with media resources available through a particular network resource. The link data 531 can enable, for example, the configuration of a link specific to the network service of the service library 530 based on an identifier specified by the user when operating the universal player. Each service library 530 may also include a list of media resources (eg, music titles, television programs or videos, movie titles, documents, etc.) available on the corresponding network service. The service rule 532 can also specify control parameters such as the number of times a user can skip a title or the number of hours a user can receive media content from a network service.

  As described in the previous example, the device interface 510 can communicate with the device to receive the IRM link 512. Link analysis 520 examines links to identify (i) network services and (ii) data items (eg, titles) to be retrieved from network services. The link analysis component 520 may use the link data 531 of a particular network service to correlate the identifier (or other aspect) (e.g., track) of the IRM link 512 with the playback link 525 of the particular service. it can. In one implementation, the link analysis component 520 obtains the playback link from the respective service library 530 by using the link data 531 to correlate the elements of the IRM link 512 to the playback link 525. In a variant, the link analysis component 520 configures the playback link 525 using the link data 531 and the elements of the IRM link 512. In yet another variation, the link analysis 520 can operate to access the identified network service's service library 530 to determine the data item or playback link 525 corresponding to the IRM link 512. The playback link 525 is communicated to the playback device 420.

  In addition, link analysis 520 also accesses service rules 532 for the identified network service to determine control parameters 527 for use with regenerative link 525. The playback link 525 and control parameter 527 are communicated back to the playback device 420 (FIG. 4) where the IRM link 512 occurred. The playback device 420 can signal the playback link 525 to a network service to receive streaming media identified by a separate playback link from a particular network service.

  FIG. 6 illustrates a method for utilizing a rights management service in accordance with one or more embodiments. Methods such as the method described in FIG. 6 may be implemented using components or elements such as those described in the embodiment of FIG. 1, FIG. 2 or FIG. Accordingly, reference may be made to previous example elements to describe suitable components or elements for performing the described steps or substeps.

  According to one or more embodiments, playback device 420 receives a token from UI device 410 (610). The playback device 420 also receives a rights management link from the UI device 410 (620). In one implementation, UI device 410 configures IRM link 512 of rights management service 430 based on a user selection or designation of a desired data item. The configured IRM link 512 can specify a network service to be used to receive the selected data item.

  The playback device 420 uses the rights management link to obtain the corresponding playback link 525 from the intermediate rights management service 430 rather than the network service itself (630). As described in other examples, rights management service 430 may provide an intermediate network interface for a number of different network services, each of which may have its own rights management rules. In providing a playback link 525 to a playback device, the intermediate rights management service 430 includes or integrates control parameters 527 that control the use of the given playback link 525 to comply with specific network service rights management rules. be able to. Referring to the example of FIG. 5, the configuration of the playback link 525 can be determined from the corresponding service library 530 along with the use of the control parameter 527.

  In this manner, rights management service 430 can determine a set of playback links 525 for a particular network service using IRM link 512 (which may be provided from playback device 420). Rights management service 430 can then communicate the set of playback links 525 to playback device 420. Rights management service 430 may also encode or specify control parameters 527 for playback link 525 based on the network service selected for playback.

  In accordance with the identified control parameters for network service 402, playback device 420 uses the playback link to receive a corresponding data item from the specified network service (640). For example, the playback device 420 can trigger the network service 402 to stream data corresponding to the individual data items to the playback device. Alternatively, the playback device 420 can download a file or document corresponding to the identified data item.

  In a variant, the UI device 410 can submit an identifier or IRM link 415 to the rights management service 430 to receive the playback link 425. The UI device 410 can then communicate the playback link 425 to the playback device 420.

  In another variation, the UI device 410 can submit an identifier or IRM link 415 to the rights management service 430, which can signal the IRM link 415 to the playback device 420. In such an implementation, communication from UI device 410 may identify playback device 420 or otherwise allow playback device 420 to receive playback link 425 directly from rights management service 430. it can.

  Hardware description

  FIG. 7A illustrates a user interface device according to one or more embodiments. By way of example, user interface device 700 receives a mobile computing device (e.g., a multi-functional cellular data / voice device), tablet, laptop, ultraportable computing device, or user input and enables direct user interaction. It can accommodate other network capable devices that are capable of doing so.

  In the example of FIG. 7A, processor 710 is coupled to input mechanism 722 and communication subsystem 730 to provide input to an external source. Exemplary input mechanism 722 includes a keyboard, touch screen, microphone, or any suitable device. Examples of communication subsystems include any suitable subsystem for transmitting and receiving data, such as a wireless port or a cellular port. Processor 710 is coupled to memory resource 734 for storing data, including incoming data, such as authorization token 131, with reference to FIG.

  The processor 710 may be configured to generate audio and visual output. For example, in the embodiment of FIG. 7A, processor 710 can provide an audio output 712 and a visual output on display 720. A user interface may be provided on the display 720 to allow user interaction with network services. The display may provide or be used in conjunction with other devices to allow the user to receive user input from the input mechanism 722.

  According to embodiments, memory resource 734 stores programs, applications, and instructions for other logic that enable functions such as those described in the examples of FIGS. For example, the memory resource 734 may include, for example, (i) instructions for accessing the network service 102 (see FIG. 1) (e.g., a client / proprietary application for a network service), (ii) e.g., a token or programmatic proof Instructions for communicating with the playback device 750 when sending a link to access media resources from the network service to the playback device, and upon receiving data (e.g., triggers, user interface events), (iii) Instructions to provide a user interface for users to interact with network services; (iv) structured links so that links identify media resources on the network services rather than links to intermediate rights management services in order to Decree, and / or (v) may store instructions 711 include instructions for communicating as a node or satellite on a personal network.

  FIG. 7B illustrates a playback or output component according to one or more embodiments. In the example of FIG. 7B, the playback device may correspond to a device dedicated to generating output for other connected devices. For example, the playback device 750 can correspond to equipment or accessory devices that have no or little mechanism for receiving user input directly. In one implementation, playback device 750 corresponds to a connected accessory for a non-connected device (e.g., non-internet television or stereo), e.g., outputs an output signal (digital or analog) for such device. Can be generated. In a variation, the playback device 750 corresponds to any computing device (eg, mobile computing device, tablet, laptop or netbook, etc.) that the user chooses to use as a playback device with the user interface device 700. be able to.

  The processor 760 of FIG. 7B is connected to other devices or computers via a network connection. In one implementation, the processor 760 generates an output data set that is output through the output component 770 or communicated to another device via one of the communication ports 782, 784 or 786.

  In the example of FIG. 7B, playback device 750 includes processor 760, memory resource 764, output component 770, and one or more communication subsystems 782, 784, 786. The output component 770 can correspond to audio and / or video output, for example. The communication subsystems 782, 784, 786 are respectively, for example, a direct connection port, a first wireless port (e.g., wireless fidelity or Bluetooth), and a second wireless port (e.g., cellular). Can be included. Accordingly, the communication subsystems 782, 784, 786 can be wireless and / or wireline. The playback device 750 can be connected to other devices or computers via connections made through the communication subsystem 782, 784 or 786. For example, in the embodiment of FIG. 7B, direct connection 782 and wireless network ports 784 and 786 allow communication with processor 760. Memory resource 764 receives (i) instructions for accessing network service 102, (ii) receiving a link to access media resources from a network service to a playback device, for example, token or programmatic proof, and Instructions to communicate with the user interface device 700 in sending data (eg, triggers, user interface events), (iii) intermediate rights management services to connect and access multiple different services and perform various actions Can store instructions 761 including instructions for operating a universal player that can utilize and / or (iv) instructions for communicating as a node or satellite on the personal network.

  Although embodiments have been described in detail herein with reference to the accompanying drawings, variations and details for particular embodiments are encompassed by the present disclosure. It is intended that the scope of the invention be defined by the appended claims and their equivalents. Furthermore, it is contemplated that particular features described individually or as part of an embodiment may be combined with other individually described features or portions of other embodiments. Thus, a lack of explanation for combinations should not preclude the inventor from claiming rights to such combinations.

100 system
102 Network services
105 links
106 Network service data items
107 User input
109 Select input
110 User interface devices, UI devices
111 Network link
112 Network service interface
113 network
114 User interface
116 Device network interface
118 Personal network registry
120 playback devices
122 Network service interface
124 Output components
125 Playback data
126 Device network interface
128 Personal network registry
131 Authorization token, token
201 Rights management service, intermediate rights management service
202 Network services
205 link, playback link
206 Network service data items, data
207 Control parameters
209 data items
210 Device network interface
211 Control link
212 Token handler
214 Link analysis
216 Outbound components
217 UI events
220 Rights Management Search component
223 Control parameters
224 Service logic
225 Device register
227 Network Service Library
229 Digital Rights Management (DRM) library, DRM library
230 Search components
232 User interface event detection component, UI event detection component
239 UI trigger
240 output components
402 Network Service
403 User input
410 UI devices
411 User interface data, data
413 tokens
415 Intermediate Rights Management (IRM) link
420 Playback device
425 Playback links
427 Control parameters
430 Intermediate Rights Management Service, Intermediate Management Service, Rights Management Service
450 Programmatic components
460 Universal player
510 Device interface
512 IRM link
520 Link analysis component, link analysis
525 Playback Links
527 Control parameters
530 Service Library
531 Link data
532 Service Rules
700 user interface devices
710 processor
711 instructions
712 audio output
720 display
722 input mechanism
730 Communication subsystem
734 Memory resources
750 playback device
760 processor
761 instructions
764 Memory resources
770 output components
782 Communication port, communication subsystem, direct connection
784 communication port, communication subsystem, wireless network port
786 Communication port, communication subsystem, wireless network port

Claims (30)

A method for utilizing network services using multiple devices, implemented by one or more processors,
Implementing an application platform shared with a second device on a first device, wherein the application platform is configured such that the first device and the second device are at least for the network service. Implemented so that it can operate to have the same identification information, and
Providing a user interface on the first device to receive input to access or use the network service;
Communicating input received from the first device in response to providing the user interface, wherein the input is communicated to the network service; and
Receiving a token from the network service in response to communicating the input;
Communicating a set of data items to the second device, wherein the set of data items is such that the second device appears to the network service as the first device; Communicating with the token and the one or more identifiers that allow the network service to be accessed and used.   The method of claim 1, further comprising accessing the network service on the second device to receive streaming media from the network service.   The method of claim 1, wherein communicating the set of data items comprises communicating a cookie stored on the first device.   The method of claim 1, wherein communicating the set of data items comprises communicating a machine identifier of the first device.   The method of claim 1, wherein receiving a token comprises receiving an authentication token.   Providing the user interface, communicating the input, receiving the token, and communicating the set of data items, respectively, using the application platform of the first device. The method of claim 1, wherein the method is performed.   The method of claim 1, further comprising controlling the second device to play streaming media from the network service according to one or more rules of the network service.   The method of claim 1, further comprising signaling one or more links identifying streaming media provided from the network service to the second device.   The method of claim 1, wherein the first device and the second device access the network service simultaneously. Receiving a trigger corresponding to a user interface event from the second device while the second device receives a plurality of links from the network service;
10. The method of claim 9, further comprising displaying user interface features corresponding to the user interface event.   Receiving the trigger from the second device comprises receiving an identifier of the user interface event; and accessing the network service using the identifier to determine the user interface characteristic. 11. The method of claim 10, comprising. A method for utilizing network services using multiple devices, implemented by one or more processors,
Implementing an application platform shared with a user interface device on a playback device, the application platform having the same identification information for at least the network service, the playback device and the user interface device Implemented so that it can operate as
Communicating with the user interface device to receive a set of data items on the playback device, wherein the set of data items is (i) a token communicated to the user interface device by the network service; And (ii) communicating with one or more identifiers used by the user interface device to access the network service;
Accessing the network service using the token and the one or more identifiers received from the user interface device.   The method of claim 12, wherein accessing the network service comprises receiving streaming media from the network service.   The method of claim 12, wherein communicating with the user interface device to receive the set of data items includes receiving a cookie stored on the first device.   The method of claim 12, wherein communicating with the user interface device to receive the set of data items comprises receiving a machine identifier of the first device.   13. The method of claim 12, wherein receiving the token includes receiving an authentication token.   13. The method of claim 12, wherein communicating with the user interface device and accessing the network service are each performed using the application platform of the playback device.   13. The method of claim 12, wherein accessing the network service is performed concurrently with the user interface device accessing the network service. Receiving a plurality of links for identifying streaming media from the user interface device;
Retrieving streaming media identified by each of the plurality of links from the network service;
Detecting the occurrence of a user interface event triggered by the network service while searching the streaming media identified by each of the plurality of links;
13. The method of claim 12, further comprising communicating data identifying the user interface event to the first device. A first device operable to provide a user interface;
A second device operable to provide a data output component;
Each of the first device and the second device implements an application platform, the application platform is such that the first device and the second device are at least the same for network services Mounted on each of the first device and the second device so that can be seen
The first device is:
Providing a user interface to receive input to access or use the network service;
Communicating received input in response to providing the user interface, wherein the input is communicated to the network service;
Receiving a token from the network service in response to communicating the input;
Communicating a set of data items to the second device, wherein the set of data items is such that the second device looks like the first device to the network service; Communicating, including the token and one or more identifiers that allow access to and use of network services;
The second device is:
Communicating with the first device to receive the set of data items;
Accessing the network service using the set of data items received from the first device.   The first device communicates a set of links to the second device, the set of links locates a corresponding set of network service data items on the network service, and the second device 21. The system of claim 20, wherein the system uses the set of links to retrieve network service data items from the network service. The second device is
Detecting the occurrence of a user interface event triggered by the network service;
Communicating data identifying the user interface event to the first device;
The first device is
21. The system of claim 20, wherein the system is responsive to the data identifying the user interface event by displaying user interface features corresponding to the user interface event.   21. The system of claim 20, wherein the set of data items includes an identifier used by the first device to initially access the network service.   24. The set of data items of claim 23, wherein the set of data items comprises one or more of (i) a cookie stored on the first device, or system.   21. The system of claim 20, wherein the token includes an authentication token.   The application for the first device to perform each of providing the user interface, communicating the input, receiving the token, and communicating the set of data items. 21. The platform of claim 20, wherein the second device uses the application platform to perform each of communicating with the first device and accessing the network service. System.   21. The system of claim 20, wherein the first device is operative to control the second device in playing streaming media from the network service according to one or more rules of the network service. .   21. The system of claim 20, wherein the first device signals one or more links identifying streaming media provided from the network service to the second device.   21. The system of claim 20, wherein the first device and the second device access the network service simultaneously. A computing device,
A memory resource that stores a set of instructions; and
Implementing an application platform shared with a second device, wherein the application platform operates such that the computing device and the second device have the same identification information for at least network services Can be implemented, implemented, and
Providing a user interface to receive input to access or use the network service;
Communicating received input in response to providing the user interface, wherein the input is communicated to the network service;
Receiving a token from the network service in response to communicating the input;
Communicating a set of data items to the second device, wherein the set of data items is such that the second device looks like the computing device to the network service. One or more processors that retrieve instructions from memory when communicating with, including the token and one or more identifiers that allow the service to be accessed and used Computing device.

Images