WO2018129181A1

WO2018129181A1 - Method, apparatus and system utilizing an nfc movie player

Info

Publication number: WO2018129181A1
Application number: PCT/US2018/012373
Authority: WO
Inventors: Rodolfo Vargas GUERRERO
Original assignee: Eye IO, LLC
Priority date: 2017-01-05
Filing date: 2018-01-04
Publication date: 2018-07-12

Abstract

Techniques and examples pertaining to streaming of digital media contents are described. A processor of a video player obtains user information of a user and metadata associated with an account of the user. The processor interacts with a content server using the user information and the metadata to receive a stream of digital media contents from the content server. The processor also interacts with a media device to cause the media device to present the stream of digital media contents.

Description

Method, Apparatus And System Utilizing An NFC Movie Player

CROSS REFERENCE TO RELATED PATENT APPLICATION(S)

[0001] The present disclosure claims the priority benefit of U.S. Provisional Patent Application No. 62/442,822, filed on January 19, 2017 and entitled "NFC Movie Player", which is herein incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure generally relates to streaming of digital media contents and, more particularly, to methods, apparatus and system pertaining to a movie player for streaming of digital media contents.

BACKGROUND

[0003] Streaming media refers to multimedia, such as digital media contents, that can be constantly provided by a vendor and presented to an end user. A user of a mobile device intending to access digital media contents is typically required to log into a user account with login credentials. For example, the user may be required to enter a user name and a password associated with the user on the mobile device. The physical act of keying in the login credentials may be cumbersome. Moreover, if a user desiring to access digital media contents is without his/her mobile device or computing device, it may not be convenient for the user to borrow someone else's mobile device or computing device to access the digital media contents. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Non-limiting and non-exhaustive embodiments of the present disclosure are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.

[0005] FIG. 1 is a diagram depicting an example implementation in accordance with an embodiment of the present disclosure.

[0006] FIG. 2 is a diagram depicting an example system architecture in accordance with an embodiment of the present disclosure.

[0007] FIG. 3 is a diagram depicting an example operation sequence in accordance with an embodiment of the present disclosure.

[0008] FIG. 4 is a block diagram depicting an example apparatus in accordance with an embodiment of the present disclosure.

[0009] FIG. 5 is a flowchart depicting an example process in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

[0010] In the following description, reference is made to the accompanying drawings that form a part thereof, and in which is shown by way of illustrating specific exemplary embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the concepts disclosed herein, and it is to be understood that modifications to the various disclosed embodiments may be made, and other embodiments may be utilized, without departing from the scope of the present disclosure. The following detailed description is, therefore, not to be taken in a limiting sense. Overview

[0011] The present disclosure proposes a near-field communication (NFC)-based system and method, herein referred to as an NFC movie player, that enables a user to stream digital media content from a remote content server to one or more media devices associated with the user. FIG. 1 illustrates an example implementation 100 in accordance with an embodiment of the present disclosure.

[0012] Referring to FIG. 1, implementation 100 may involve a movie card 110 (herein interchangeably referred to as an NFC card), a remote control 120, and a video player 130. Movie card 110 may be configured with wireless communication features in compliance with the NFC protocols. Movie card 110 may be implemented with a passive device which does not contain any power supply or power source. Movie card 110 may contain digitally-stored information about specific media content(s) stored on a remote content server (not shown).

[0013] Remote control 120 may be implemented with an active NFC device, which may be configured to interrogate movie card 110 and retrieve information from movie card 110. The retrieved information may be in raw data, encrypted and/or authenticated. Remote control 120 may include a number of subsystems such as, for example and without limitation, a central processing unit (CPU) capable of data and information processing, a random-access memory (RAM) capable of temporary data storage, a nonvolatile memory (herein interchangeably referred to as storage) capable of long-term data storage, a wireless communication module (e.g., Bluetooth module) capable of wireless connectivity (e.g., wireless connection in compliance with Bluetooth 4.0, WiFi or Direct WiFi), and an NFC transceiver capable of wireless communications via NFC with movie card 110. [0014] Video player 130 may include a number of subsystems such as, for example and without limitation, a CPU capable of data and information processing, a RAM capable of temporary data storage, a nonvolatile memory (herein interchangeably referred to as storage) capable of long-term data storage, and a wireless communication module (e.g., Bluetooth module) capable of wireless connectivity (e.g., wireless connection in compliance with Bluetooth 4.0). Accordingly, a wireless Bluetooth link may be established between remote control 120 and video player 130 using, for example, Bluetooth 4.0. Video player 130 may be configured to communicatively connect to a remote content server, validate a user account of a user, and stream any requested media content (herein interchangeably referred to as assets) to one or more media devices such as, for example and without limitation, television sets associated with the user.

[0015] Under the proposed system and method of the present disclosure, movie card 110 may contain a code that allows the user to access the assets associated with movie card 110. When the user purchases, rents or otherwise obtains movie card 110, movie card 110 may first need to be activated by the user. In some embodiments, activation may be done by the user physically placing movie card 110 in the proximity of remote control 120. Using NFC communication, movie card 110 and remote control 120 may exchange relevant data/information. Accordingly, remote control 120 may receive information from movie card 110 such as, for example and without limitation, asset ID which is the identifier to the media content with which movie card 110 is associated. Remote control 120 may then transmit this information, e.g., over a Bluetooth 4.0 link, to video player 130. Video player 130 may connect to the remote content server (not shown) associated with the media content, validate movie card 110, validate a distant between the remote control 120 and video player 130 (e.g., using Bluetooth 4.0 Radio link power algorithms), validate User Smart Phone's Bluetooth Mac addresses in case that remote control 120 is on proximity to the video player 130, and link movie card 110 to the user account of the user. At the user's option, video player 130 may begin playback of the requested media content on a media device (e.g., television set) associated with the user. After movie card 110 has been initialized, media playback may be initialized at any time by the user bringing movie card 110 in the proximity of remote control 120 and video player 130 that are associated with the user's account.

[0016] Once movie card 110 is initialized and linked to the user account of the user, the user is authorized and thus it is the user, but no one else, who can access the assets associated with movie card 110. This security feature may prevent an unauthorized person who steals or obtains an initialized card associated with an account not belonging to the unauthorized person from performing an unauthorized access to the media assets. In some embodiments, movie card 110 may present trailers or advertising to a person other than the authorized user of the card, allowing the unauthorized person to purchase the movie or any other services in the advertisements. In some embodiments, advertising messages may also be included as a part of the streamed assets, as decided by the vendor of the assets. Furthermore, different options may be made available to a user, such as renting versus purchasing, limited-time rentals, different tiers of membership (e.g., with different amounts of advertising), and so on.

[0017] FIG. 2 illustrates an example system architecture 200 in accordance with an embodiment of the present disclosure. Referring to FIG. 2, system architecture 200 may involve a movie card 210, a remote control 220, a video player 230, a media device 240, a communication device 250, a network 260, and a remote content server 270. In system architecture 200, movie card 210 may be implemented by movie card 110 described above, remote control 220 may be implemented by remote control 120 described above, and video player 230 may be implemented by video player 130 described above. In some embodiments, video player 230 may be implemented in the form of a dongle, media device 240 may be implemented in the form of a television set, and communication device 250 may be implemented in the form of a Wi-Fi access point. In some embodiments, remote control 220 may be a portable device or a wearable device such as, for example and without limitation, a smartphone, a tablet computer, a laptop computer, a notebook computer, a smartwatch, a smart bracelet or the like. In some embodiments, instead of being two discrete and separate components, remote control 220 and video player 230 may be implemented in as one single electronic device.

[0018] As shown in FIG. 2, video player 230 may be interfaced with media device 240 located at a user premise, herein referred to as the client location. Also, remote control 220 may be communicatively connected with video player 230 using, for example and without limitation, a wireless Bluetooth interface. Video player 230 may be further connected to network 260 (e.g., the Internet) via communication device 250 at the client location. The interface between video player 230 and communication device 250 may be achieved by, for example and without limitation, interfacing video player 230 with a user mobile device (not shown), where the user mobile device executes an application software that allows initialization of video player 230 to access network 260 via communication device 250. Video player 230 may communicate with content server 270 associated with a streaming content. In system architecture 200, movie card 210 may communicate with remote control 220 using an NFC interface as described above with respect to FIG. 1. Additionally, remote control 220 and video player 230 may communicate using any suitable wireless protocols and/or standards such as, for example and without limitation, Wi-Fi, Bluetooth (e.g., Bluetooth 4.0), iBeacon or the like. Similarly, video player 230 and communication device 250 may communicate using any suitable wireless protocols and/or standards such as, for example and without limitation, Wi-Fi, Bluetooth (e.g., Bluetooth 4.0), iBeacon or the like. The sequence of operations associated with streaming media content based on video player 230 is depicted in FIG. 3.

[0019] FIG. 3 illustrates an example operation sequence 300 in accordance with an embodiment of the present disclosure. It is noteworthy that operation sequence 300 is based on the assumption that video player 230 has been appropriately initialized to interface with communication device 250. Referring to FIG. 3, operation sequence 300 associated with video player 230 may include a number of steps or operations, as described below.

[0020] At step 1 (denoted as "(1)" in FIG. 3), movie card 210, as a passive NFC device, may await initialization from remote control 220, which is an active NFC device. As described above, movie card 210 may store therein data, or metadata, associated with a particular asset (e.g., video asset or digital media content) on content server 270.

[0021] At step 2 (denoted as "(2)" in FIG. 3), when movie card 210 is within proximity of a paired NFC device, or remote control 220 in this case, movie card 210 and remote control 220 may establish wireless communication to pair and exchange data. The metadata associated with the asset may be transferred from movie card 210 to remote control 220.

[0022] At step 3 (denoted as "(3)" in FIG. 3), remote control 220 may pair with video player 230 may establish wireless communication to pair. For example, the pairing process between remote control 220 and video player 230 may be via a standard iBeacon Bluetooth interface.

[0023] At step 4 (denoted as "(4)" in FIG. 3), remote control 220 may transmit the metadata and associated user information of user of movie card 210 to video player 230.

[0024] At step 5 (denoted as "(5)" in FIG. 3), video player 230 may interface with media device 240 (e.g., a television set). For example, video player 230 and media device 240 may establish communication using a Consumer Electronics Control (CEC) interface as featured on a High-Definition Multimedia Interface (HDMI).

[0025] At step 6 (denoted as "(6)" in FIG. 3), video player 230 may interface with content server 270 (e.g., via communication device 250 and network 260), which may contain the asset. Moreover, video player 230 as well as a user account associated with the user of movie card 210 may be authenticated.

[0026] At step 7 (denoted as "(7)" in FIG. 3), video player 230 may transmit the metadata from movie card 210 to content server 270, on which a card service application may validate movie card 210, the asset and product definition.

[0027] At step 8 (denoted as "(8)" in FIG. 3), in an event that the validation process at step 7 is successful, content server 270 may instruct or otherwise authorize video player 230 to play the asset. Alternatively, content server 270 may provide the user with secondary actins such as, for example and without limitation, playing the asset at a specific time, rending the asset instead of purchasing it, and so on.

[0028] At step 9 (denoted as "(9)" in FIG. 3), in an event that media device 240 is off, video player 230 may turn on or otherwise activate media device 240 (e.g., by using the HDMI- CEC power-on command).

[0029] At step 10 (denoted as "(10)" in FIG. 3), video player 230 may set the appropriate HDMI-CEC input on media device 240.

[0030] At step 11 (denoted as "(11)" in FIG. 3), content server 270 may stream the asset to media device 240 for playback via video player 230.

[0031] Advantageously, the combination of movie card 210, remote control 220 and video player 230 offers a convenient and portable way for a user to have access to his/her library of digital media contents from any location with a suitable network connection and a media device (e.g., television set). Moreover, the proposed arrangement provides a vendor of video assets

[0032] The combination of a movie card (e.g., movie card 110 or movie card 210), a remote control (e.g., remote control 120 or remote control 220) and a video player (e.g., video player 130 or video player 230) presents a very convenient and portable way for a user to have access to his/her media library from anywhere there is a suitable Internet connection and a television set. Similarly, this arrangement offers a vendor of video assets flexibility in providing different product options to a user such as rentals, direct purchases, pay-per-view, and so on.

Example Applications

[0033] In view of the above, the present disclosure may be applicable to a variety of products such as, for example and without limitation, rental assets, subscription to assets, single assets, high-value premium assets, and event assets. Specifically, the notion of "rental assets" may refer to the option for a user to rent a particular video or other media asset. The notion of "subscription to assets" may refer to the scenario in which a user may be given the option to access assets on a paid subscription basis. The notion of "single assets" may refer to a single purchase for a single asset, such as the purchase of a single movie title. The notion of "high-value premium assets" may refer to video assets that are the latest releases and/or in-demand media, for example, which may be offered as high-value premium assets. The notion of "event assets" may refer to event-based or event-related assets such as, for example and without limitation, sports, televised broadcasts, concerts and other real-time events.

[0034] In terms of deployment, various embodiments of the present disclosure may be deployed in a variety of types of deployment. In a "first device connected" type of deployment, a movie card (e.g., movie card 110 or movie card 210) may be locked to a first device (e.g., remote control 120 or remote control 220) and associated user account with which it is paired. Accordingly, any attempt to subsequently pair with a different device may yield none or limited functionality. For example, a movie card associated with a single purchase of a movie may play the movie when paired with the remote control and video player with which it is associated. In an event that either of the latter two devices is changed, the movie card may enable only trailers, with the option to purchase the movie. In a "pre-registered" type of deployment, a movie card may be pre-regi stered to a user account at the time of purchase. A user account may be also associated with a specific remote control and video player. Pre-regi strati on may link the movie card with these two devices (movie card and remote control) at the time of purchase.

[0035] In terms of location, various embodiments of the present disclosure may be implemented in a variety of locations such as, for example and without limitation, home, office or second home, Airbnb, hotel or rented/leased property, and mobile device. In an event that the location is home, the location may be the home of a user, where functionality may be enabled with multiple television sets. In an event that the location is office or second home, the portability of the movie card, the remote control and the video player may allow a user to access any purchased assets in an office or a second home. Alternatively, multiple sets of remote controls and movie players may be linked to a single user account, with deployment and multiple locations. In an event that the location is hotel or a rented/leased property, a traveler may take his/her collection of movie cards, a remote control and video player with the traveler. The video player may be interfaced with an available internet connection and, when plugged into a television set, may validate a user account and enable asset access from that location. In an event that the location is a mobile device, assets may also be streamed to a mobile device instead of the television set. The mobile device may need to be appropriately registered and linked to the user account via, for example, an application software package running on the mobile device.

Illustrative Embodiments

[0036] FIG. 4 illustrates an example apparatus 400 in accordance with an embodiment of the present disclosure. Apparatus 400 may be an example implementation of video payer 130 and/or video player 230. For instance, apparatus 400 may be implemented in a dongle. Alternatively, apparatus 400 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more complex-instruction-set-computing (CISC) processors. Apparatus 400 may include at least some of those components shown in FIG. 4 such as a processor 410, for example. Apparatus 400 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply), and, thus, such component(s) of apparatus 400 are neither shown in FIG. 4 nor described below in the interest of simplicity and brevity.

[0037] In one aspect, processor 410 may be implemented in the form of one or more single- core processors, one or more multi-core processors, or one or more CISC processors. That is, even though a singular term "a processor" is used herein to refer to processor 410, processor 410 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, processor 410 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, processor 410 is a special - purpose machine specifically designed, arranged and configured to perform specific tasks including streaming of digital media contents in accordance with various implementations of the present disclosure.

[0038] Referring to FIG. 4, apparatus 400 may also include a first wireless communication circuit 420, a second wireless communication circuit 430, and an interface circuit 440. First wireless communication circuit 420 may be capable of communicating with a remote control (e.g., remote control 120 and/or remote control 220). Second wireless communication circuit 430 may be capable of communicating with a wireless communication device (e.g., communication device 250). Interface circuit 440 may be capable of communicating with a media device (e.g., media device 240). Processor 410 may be coupled to control operations of first wireless communication circuit 420, second wireless communication circuit 430, and interface circuit 440.

[0039] In some embodiments, processor 410 may be capable of obtaining, from the remote control, user information of a user and metadata associated with an account of the user from the remote control. Processor 410 may be also capable of interacting, via the wireless communication device, with a content server (e.g., content server 270) using the user information and the metadata to receive a stream of digital media contents from the content server. Processor 410 may be further capable of interacting with the media device to cause the media device to present the stream of digital media contents.

[0040] In some embodiments, first wireless communication circuit 420 may communicate with the remote control using an NFC protocol or a Bluetooth protocol (e.g., Bluetooth 4.0). Moreover, second wireless communication circuit 430 may communicate with the wireless communication device using an IEEE 802.11-based protocol such as Wi-Fi, for example. [0041] In some embodiments, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, processor 410 may perform a number of operations. For instance, processor 410 may transmit, via second wireless communication circuit 430, the user information of the user and device information of the video player to the content server. Additionally, processor 410 may receive, from the content server via second wireless communication circuit 430, an indication that the user and the video player are authenticated by the content server.

[0042] In some embodiments, in obtaining the user information and the metadata, processor 410 may obtain the user information and the metadata from a movie card via the remote control. Furthermore, the metadata may identify a video asset comprising the digital media contents.

[0043] In some embodiments, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, processor may perform a number of additional operations. For instance, processor 410 may transmit, via second wireless communication circuit 430, the metadata to the content server. Moreover, processor 410 may receive, from the content server via second wireless communication circuit 430, an indication that the movie card and the video asset are validated by the content server.

[0044] In some embodiments, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, processor 410 may further perform a number of operations. For instance, processor 410 may receive, via second wireless communication circuit 430, an instruction from the content server. The instruction may include one of the following: (1) an instruction that causes the movie player to play the video asset, (2) an instruction that indicates a specific time for playing the video asset, or (3) an instruction that instructs the user to purchase or rent the video asset.

[0045] In some embodiments, in interacting with the media device to cause the media device to present the stream of digital media contents, processor 410 may perform a number of operations. For instance, processor 410 may establish, via interface circuit 440, communications with the media device. Moreover, processor 410 may transmit, to the media device via interface circuit 440, the stream of digital media contents received from the content server. In some embodiments, in establishing communications with the media device, processor 410 may communicate with the media device using a Consumer Electronics Control (CEC) feature of a High-Definition Multimedia Interface (HDMI) interface of the media device.

[0046] In some embodiments, in interacting with the media device to cause the media device to present the stream of digital media contents, processor 410 may additionally perform a number of operations. For instance, processor 410 may determine whether the media device is on or off. Furthermore, processor 410 may activate the media device to turn on the media device responsive to a determination that the media device is off. In some embodiments, in activating the media device, processor 410 may activate the media device via a HDMI-CEC power-on command.

[0047] FIG. 5 illustrates an example process 500 in accordance with the present disclosure. Process 500 may represent an aspect of implementation 100, system architecture 200, operation sequence 300 and/or apparatus 400 described above. Process 500 may include one or more operations, actions, or functions shown as blocks such as 510, 520 and 530. Although illustrated as discrete blocks, various blocks of process 500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, blocks of process 500 may be implemented in the order shown in FIG. 5 and, alternatively, in a different order. For illustrative purpose and without limitation, process 500 is described below in the context of apparatus 400 being implemented in or as video player 230 in system architecture 200. Process 500 may begin with block 510.

[0048] At 510, process 500 may involve processor 410 of apparatus 400, as video player 230, obtaining user information of a user and metadata associated with an account of the user. Process 500 may proceed from 510 to 520.

[0049] At 520, process 500 may involve processor 410 interacting with content server 270 using the user information and the metadata to receive a stream of digital media contents from content server 270. Process 500 may proceed from 520 to 530.

[0050] At 530, process 500 may involve processor 410 interacting with media device 240 to cause media device 240 to present the stream of digital media contents to the user.

[0051] In some embodiments, in obtaining the user information and the metadata, process 500 may involve processor 410 wirelessly receiving, via first wireless communication circuit 420, the user information and the metadata from a passive device (e.g., movie card 210).

[0052] In some embodiments, in wirelessly receiving the user information and the metadata from the passive device, process 500 may involve processor 410 wirelessly receiving, via first wireless communication circuit 420, the user information and the metadata from the passive device using an NFC protocol.

[0053] Alternatively, in wirelessly receiving the user information and the metadata from the passive device, process 500 may involve processor 410 wirelessly receiving, via first wireless communication circuit 420, the user information and the metadata from an active device (e.g., remote control 220) which retrieves the user information and the metadata from the passive device (e.g., movie card 210). In some embodiments, in wirelessly receiving the user information and the metadata from the active device, process 500 may involve processor 410 wirelessly receiving, via first wireless communication circuit 420, the user information and the metadata from the active device using a Bluetooth protocol.

[0054] In some embodiments, in interacting with content server 270 using the user information and the metadata to receive the stream of digital media contents from content server 270, process 500 may involve processor 410 performing a number of operations. For instance, process 500 may involve processor 410 transmitting the user information of the user and device information of the video player to content server 270. Additionally, process 500 may involve processor 410 receiving, from content server 270, an indication that the user and the video player are authenticated by content server 270.

[0055] In some embodiments, in obtaining the user information and the metadata, process 500 may involve processor 410 obtaining the user information and the metadata from a movie card (e.g., movie card 210). Additionally, the metadata may identify a video asset that includes the digital media contents. Moreover, in interacting with content server 270 using the user information and the metadata to receive the stream of digital media contents from content server 270, process 500 may involve processor 410 performing a number of operations. For instance, process 500 may involve processor 410 transmitting the metadata to content server 270. Furthermore, process 500 may involve processor 410 receiving, from content server 270, an indication that the movie card and the video asset are validated by content server 270.

[0056] In some embodiments, in interacting with content server 270 using the user information and the metadata to receive the stream of digital media contents from content server 270, process 500 may involve processor 410 receiving an instruction from content server 270. The instruction may include one of the following: (1) an instruction that causes the movie player to play the video asset, (2) an instmction that indicates a specific time for playing the video asset, or (3) an instruction that instructs the user to purchase or rent the video asset.

[0057] In some embodiments, in interacting with media device 240 to cause media device 240 to present the stream of digital media contents, process 500 may involve processor 410 performing a number of operations. For instance, process 500 may involve processor 410 establishing communications with media device 240. Moreover, process 500 may involve processor 410 transmitting, to media device 240, the stream of digital media contents received from content server 270. In some embodiments, in establishing communications with media device 240, process 500 may involve processor 410 communicating with media device 240 using a CEC feature of a HDMI interface of media device 240.

[0058] In some embodiments, in interacting with media device 240 to cause media device 240 to present the stream of digital media contents, process 500 may further involve processor 410 performing a number of operations. For instance, process 500 may involve processor 410 determining whether media device 240 is on or off. Moreover, process 500 may involve processor 410 activating media device 240 to turn on media device 240 responsive to a determination that media device 240 is off. In some embodiments, in activating media device 240, process 500 may involve processor 410 activating media device 240 via a UDMI-CEC power-on command.

Additional Notes

[0059] In the above disclosure, reference has been made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific implementations in which the present disclosure may be practiced. It is understood that other implementations may be utilized, and structural changes may be made without departing from the scope of the present disclosure. References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0060] Implementations of the systems, apparatuses, devices, and methods disclosed herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed herein. Implementations within the scope of the present disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, implementations of the present disclosure can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media.

[0061] Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives ("SSDs") (e.g., based on RAM), Flash memory, phase-change memory ("PCM"), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

[0062] An implementation of the devices, systems, and methods disclosed herein may communicate over a computer network. A "network" is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or any combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

[0063] Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general-purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[0064] Those skilled in the art will appreciate that the present disclosure may be practiced in network computing environments with many types of computer system configurations, including, an in-dash vehicle computer, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by any combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

[0065] Further, where appropriate, functions described herein can be performed in one or more of: hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein. Certain terms are used throughout the description and claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name, but not function.

[0066] It should be noted that the sensor embodiments discussed above may comprise computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functions. For example, a sensor may include computer code configured to be executed in one or more processors, and may include hardware logic/electrical circuitry controlled by the computer code. These example devices are provided herein purposes of illustration, and are not intended to be limiting. Embodiments of the present disclosure may be implemented in further types of devices, as would be known to persons skilled in the relevant art(s). [0067] At least some embodiments of the present disclosure have been directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer useable medium. Such software, when executed in one or more data processing devices, causes a device to operate as described herein.

[0068] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the present disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the aforementioned alternate implementations may be used in any combination desired to form additional hybrid implementations of the present disclosure.

Claims

1. A method, comprising:

obtaining, by a processor of a video player, user information of a user and metadata associated with an account of the user;

interacting, by the processor, with a content server using the user information and the metadata to receive a stream of digital media contents from the content server; and

interacting, by the processor, with a media device to cause the media device to present the stream of digital media contents.

2. The method of claim 1, wherein the obtaining of the user information and the metadata comprises wirelessly receiving the user information and the metadata from a passive device.

3. The method of claim 2, wherein the wirelessly receiving of the user information and the metadata from the passive device comprises wirelessly receiving the user information and the metadata from the passive device using a near-field communication (NFC) protocol.

4. The method of claim 2, wherein the wirelessly receiving of the user information and the metadata from the passive device comprises wirelessly receiving the user information and the metadata from an active device which retrieves the user information and the metadata from the passive device.

5. The method of claim 4, wherein the wirelessly receiving of the user information and the metadata from the active device comprises wirelessly receiving the user information and the metadata from the active device using a Bluetooth protocol.

6. The method of claim 1, wherein the interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server comprises:

transmitting the user information of the user and device information of the video player to the content server; and

receiving, from the content server, an indication that the user and the video player are authenticated by the content server.

7. The method of claim 6, wherein the obtaining of the user information and the metadata comprises obtaining the user information and the metadata from a movie card, wherein the metadata identifies a video asset comprising the digital media contents, and wherein the interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server further comprises:

transmitting the metadata to the content server; and

receiving, from the content server, an indication that the movie card and the video asset are validated by the content server.

8. The method of claim 7, wherein the interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server further comprises:

receiving an instruction from the content server,

wherein the instruction comprises one of:

an instruction that causes the movie player to play the video asset; an instruction that indicates a specific time for playing the video asset; or an instruction that instructs the user to purchase or rent the video asset.

9. The method of claim 1, wherein the interacting with the media device to cause the media device to present the stream of digital media contents comprises:

establishing communications with the media device; and

transmitting, to the media device, the stream of digital media contents received from the content server.

10. The method of claim 9, wherein the establishing of communications with the media device comprises communicating with the media device using a Consumer Electronics Control (CEC) feature of a High-Definition Multimedia Interface (HDMI) interface of the media device.

11. The method of claim 9, wherein the interacting with the media device to cause the media device to present the stream of digital media contents further comprises:

determining whether the media device is on or off; and activating the media device to turn on the media device responsive to a determination that the media device is off.

12. The method of claim 11, wherein the activating of the media device comprises activating the media device via a High-Definition Multimedia Interface-Consumer Electronics Control (HDMI-CEC) power-on command.

13. An apparatus, comprising:

a first wireless communication circuit capable of communicating with a remote control; a second wireless communication circuit capable of communicating with a wireless communication device;

an interface circuit capable of communicating with a media device;

a processor coupled to control operations of the first wireless communication circuit, the second wireless communication circuit, and the interface circuit, the processor capable of performing operations comprising:

obtaining, from the remote control, user information of a user and metadata associated with an account of the user from the remote control;

interacting, via the wireless communication device, with a content server using the user information and the metadata to receive a stream of digital media contents from the content server; and

interacting with the media device to cause the media device to present the stream of digital media contents.

14. The apparatus of claim 13, wherein the first wireless communication circuit communicates with the remote control using a near-field communication (NFC) protocol or a Bluetooth protocol, and wherein the second wireless communication circuit communicates with the wireless communication device using an Institute of Electrical and Electronics Engineers (IEEE) 802.11-based protocol.

15. The apparatus of claim 13, wherein, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, the processor performs operations comprising:

16. The apparatus of claim 15, wherein, in obtaining the user information and the metadata, the processor obtains the user information and the metadata from a movie card via the remote control, and wherein the metadata identifies a video asset comprising the digital media contents.

17. The apparatus of claim 16, wherein, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, the processor further performs operations comprising: transmitting, via the second wireless communication circuit, the metadata to the content server; and

receiving, from the content server via the second wireless communication circuit, an indication that the movie card and the video asset are validated by the content server.

18. The apparatus of claim 17, wherein, in interacting with the content server using the user information and the metadata to receive the stream of digital media contents from the content server, the processor further performs operations comprising:

receiving, via the second wireless communication circuit, an instruction from the content server,

wherein the instruction comprises one of:

19. The apparatus of claim 13, wherein, in interacting with the media device to cause the media device to present the stream of digital media contents, the processor performs operations comprising:

establishing, via the interface circuit, communications with the media device; and transmitting, to the media device via the interface circuit, the stream of digital media contents received from the content server, wherein the establishing of communications with the media device comprises communicating with the media device using a Consumer Electronics Control (CEC) feature of a High-Definition Multimedia Interface (HDMI) interface of the media device.

20. The apparatus of claim 19, wherein, in interacting with the media device to cause the media device to present the stream of digital media contents, the processor further performs operations comprising:

determining whether the media device is on or off; and

activating the media device to turn on the media device responsive to a determination that the media device is off,

wherein the activating of the media device comprises activating the media device via a HDMI-CEC power-on command.