The present disclosure relates to systems and methods of licensing access to digital content.
Digital content such as computer software products, video games, music, and any other media capable of being embodied in digital format may be sold or licensed to an end user customer. For example, the right to copy, access, or execute the digital content may be licensed to a user and a provider or vendor may retain ownership of the rights to the content. Accordingly, it may be desirable to provide unit-based licensing for third party access of digital content.
Disclosed herein are aspects, features, elements, implementations, and embodiments of unit-based licensing for third party access of digital content.
In an embodiment, a method of unit-based licensing for third party access of digital content is disclosed. Unit-based licensing for third party access of digital content may include receiving a request for access to content, the request for access indicating the customer account and a third party, identifying a cardinality of assigned units for the content, identifying a cardinality of available licensing units allocated to the customer account, determining, by a processor, whether the cardinality of the assigned units is within the cardinality of available licensing units, outputting a response indicating that the request is granted on a condition that the cardinality of the assigned units is within the cardinality of available licensing units, and outputting a response indicating that the request is denied on a condition that the cardinality of the assigned units exceeds the cardinality of available licensing units.
In another embodiment, an apparatus for unit-based licensing for third party access of digital content is disclosed. The apparatus may include a non-transitory computer readable memory and a processor configured to execute instructions stored on the memory to receive a request for access to content, the request for access indicating a customer account and a third party, identify a cardinality of assigned units for the content, identify a cardinality of available licensing units allocated to the customer account, determine whether the cardinality of the assigned units is within the cardinality of the available licensing units, output a response indicating that the request is granted on a condition that the cardinality of the assigned units is within the cardinality of the available licensing units, and output a response indicating that the request is denied on a condition that the cardinality of the assigned units exceeds the cardinality of the available licensing units.
In another embodiment, a method of accessing digital content using unit-based licensing by a third party is disclosed. Accessing digital content using unit-based licensing by a third party may include transmitting, by a processor in response to instructions stored on a non-transitory computer readable medium, a request for access to content, the request for access indicating a customer account and a third party, receiving a response indicating that the request is granted on a condition that a cardinality of assigned units for the content is within a cardinality of available licensing units allocated to the customer account, and receiving a response indicating that the request is denied on a condition that the cardinality of the assigned units exceeds the cardinality of the available licensing units.
Variations in these and other aspects, features, elements, implementations, and embodiments of the methods, apparatus, procedures, and algorithms disclosed herein are described in further detail hereafter.
The description herein makes reference to the accompanying drawings wherein like reference numerals refer to like parts throughout the several views, and wherein:
A creator or owner of content, such as digital content or live-performance content, may control access to the content by licensing the content to end users. For example, licensing may include controlling the right to display, perform, distribute, or reproduce the content. Unit-based licensing may include licensing that controls access to content by allocating licensing units to a customer account, such that one or more licensing units may be redeemed or charged to access one or more digital content objects.
Unit-based licensing for third party access of digital content may include controlling access to content by one or more third parties via a customer system. For example, a third party device may send a request for access to content to the provider via a customer system and licensing units allocated to the customer system may be redeemed in exchange for access to the content by the third party.
The aspects, features, elements, and embodiments of methods, procedures, or algorithms disclosed herein, or any part or parts thereof, may be implemented in a computer program, software, or firmware incorporated in a non-transitory computer-readable storage medium for execution by a general purpose or special purpose computer or processor, and may be implemented as a computer program product, such as a computer program product accessible from a tangible computer-usable or computer-readable medium.
As used herein, the terminology “computer” or “device” includes any unit, or combination of units, capable of performing any method, or any portion or portions thereof, disclosed herein. Devices may further include mobile devices that may include user equipment, a wireless transmit/receive unit, a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a mobile environment.
As used herein, the terminology “processor” includes a single processor or multiple processors, such as one or more general purpose processors, one or more special purpose processors, one or more conventional processors, one or more digital signal processors, one or more microprocessors, one or more controllers, one or more microcontrollers, one or more Application Specific Integrated Circuits (ASICs), one or more Application Specific Standard Products (ASSPs); one or more Field Programmable Gate Arrays (FPGAs) circuits, any other type or combination of integrated circuits (ICs), one or more state machines, or any combination thereof.
As used herein, the terminology “memory” includes any computer-usable or computer-readable medium or device that can, for example, tangibly contain, store, communicate, or transport any signal or information for use by or in connection with any processor. Examples of computer-readable storage mediums may include one or more read only memories, one or more random access memories, one or more registers, one or more cache memories, one or more semiconductor memory devices, one or more magnetic media, such as internal hard disks and removable disks, one or more magneto-optical media, one or more optical media such as CD-ROM disks, and digital versatile disks (DVDs), or any combination thereof.
As used herein, the terminology “example”, “embodiment”, “implementation”, “aspect”, “feature”, or “element” indicate serving as an example, instance, or illustration. Unless expressly indicated, any example, embodiment, implementation, aspect, feature, or element is independent of each other example, embodiment, implementation, aspect, feature, or element and may be used in combination with any other example, embodiment, implementation, aspect, feature, or element.
As used herein, the terminology “determine” and “identify”, or any variations thereof, includes selecting, ascertaining, computing, looking up, receiving, determining, establishing, obtaining, or otherwise identifying or determining in any manner whatsoever using one or more of the devices shown and described herein. As used herein, the terminology “cardinality” includes a number or count of elements or items in a set, group, plurality, or any other collection of zero or more elements.
As used herein, the terminology “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to indicate any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
As used herein, the terminology “digital content” may include computer software programs, video games, music, movies, videos, or any other media that may be embodied in digital form, and which may be accessed, downloaded, input, or otherwise transferred to a computer or processor. Digital content may include digital data or digital files that may be processed by external application programs or may be executed by external software, hardware, or both. As used herein, the terminology “content” may include live content or fixed content. Fixed content may include any content that may be presented from a tangible storage medium, such as digital content. Live content, or live-performance content, may include any content that may be accessed substantially concurrently with the creation or generation of the content, such as the presentation of a movie in a movie theater, a concert, a sporting event, a gallery display, or any other live event.
As used herein, the terminology “event” may include any presentation, distribution, or display of content capable of concurrent, or nearly concurrent, access by multiple users. For example, an event may include a physical presentation, such a presentation at a movie theater, concert hall, museum, or restaurant, or a virtual presentation, such as a broadcast over the Internet or a television broadcast. Although described as unit-based licensing for third party access of digital content, implementations of this disclosure may apply to unit-based licensing for third party content access.
As used herein, the terminology “access” or “accessing” may include presenting, downloading, executing, streaming, or otherwise interacting, or enabling interaction, with a content object. In some embodiments, digital content objects may be executed, stored, or both, at a provider location. In some embodiments, digital content objects may be stored locally on a customer network or customer device and the digital content objects may be executed or run on the customer network or device.
In some embodiments, a node based license may indicate that content is accessible by a unique device, such as a computer, a unique account, such as an account associated with an individual user, or a combination of a unique device and a unique account. In some embodiments, a network based license may indicate that content is accessible by one or more devices within a specified network. For example, a defined number of devices within the network may concurrently access the content. In some embodiments, a license, including a node based license or a network based license, may be associated with a unique content object, or with a suite of related content objects.
As used herein, the terminology “assigned units”, “price”, “licensing price” or variations thereof, may include an assigned number of licensing units that may be exchanged or redeemed to access a particular content object. As used herein, the terminology “licensed units” or “allocated units” may refer to a total number of units provided to a customer or customer group. As used herein, the terminology “checked out units”, “redeemed units”, or “exchanged units” may refer to assigned units charged to a customer for digital content being accessed. “Available units” may refer to a difference between licensed units and checked out units. In some embodiments, licensing units may be temporarily or permanently exchanged for access. Temporarily exchanged licensing units may be returned to the pool of available units associated with the customer upon termination or completion of content access.
Further, for simplicity of explanation, although the figures and descriptions herein may include sequences or series of steps or stages, elements of the methods disclosed herein may occur in various orders or concurrently. Additionally, elements of the methods disclosed herein may occur with other elements not explicitly presented and described herein. Furthermore, not all elements of the methods described herein may be required to implement a method in accordance with this disclosure. Although aspects, features, and elements are described herein in particular combinations, each aspect, feature, or element may be used independently or in various combinations with or without other aspects, features, and elements.
In some embodiments, customer system 110 may be associated with an individual user or customer, and the user may access content using licensing units allocated to the user. In some embodiments, customer system 110 may comprise devices and networks through which a customer or user may access digital content from provider 120. For example, as shown in
In some implementations, customer system 110 may be associated with a collection or group of customers, or members, and shared licensing units may be allocated to the group. For example, a group may include one or more families, a classroom of students, a small business, a social group, or any other organization capable of licensing content such that members of the group are capable of accessing the content.
In some embodiments, elements of the customer system 110, such as customer network 160 and customer device 170, may communicate with each other or with elements external to the customer system 110, such as the provider 120. For example, customer network 160 and customer device 170 may independently communicate through communication network 130.
In some embodiments, customer network 160 may include one or more individual nodes 162/164, a customer server 166, a host processor (CPU) 168, or any combination thereof. A node 162/164 may be a device, such as a computer, and may access digital content. For example, a node 162/164 may access digital content in response to user input. Although
In some embodiments, customer device 170 may be any device, such as a computer or mobile device, capable of accessing digital content. In some embodiments, a customer device 170 may include a processor, such as CPU 172.
In some embodiments, provider 120 may be a device or system configured to provide access to digital content to one or more licensed customers. For example, provider 120 may include an Internet Protocol (IP) network-based unit, such as a website service, that implements methods for controlling access to digital content. In some embodiments, provider 120 may provide customer system 110 access to digital content objects, which may be included in a suite of digital content. Although
In some implementations, unit-based licensing for digital content may include communication between the customer system 110 and the provider 120 via the communication network 130. The communication network 130 may be a local area network (LAN), wide area network (WAN), virtual private network (VPN), a mobile or cellular telephone network, the Internet, or any other electronic communication medium. Although not explicitly shown in
In some embodiments, a license manager (LM) 140 may be included in the communication system 100. License manager 140 may control the access to digital content provided by provider 120. Although shown as a separate unit, in some embodiments, license manager 140 may be incorporated with provider 120, customer system 110, or both. In some embodiments, the license manager 140 may monitor content access for the customer system 110. For example, the license manager 140 may detect the termination or conclusion of access to content.
In some embodiments, license manager 140 may generate and maintain a log. The log may include a record of a number of available units that may be used by the customer system 110 at any given time. In some embodiments, the license manager 140 may update the log for each change of the available units for customer system 110. For example, the log may be updated to indicate a change in the available units in response to the accessing of digital content from provider 120, the termination of the access of digital content, or a change in pricing of digital content being accessed by the customer. In some embodiments, the log may be a file, or database, stored in a memory in communication with provider 120 or license manager 140.
In some embodiments, the communication system 100 may include a third party device 150, which may be a device, such as a computer or mobile device, capable of accessing digital content. Although not shown in
In some embodiments, unit-based licensing for third party access of digital content may include controlling access to digital content in response to a request to access the digital content from a third party device via a customer system, or from an authorized device via a third party network.
In some embodiments, unit-based licensing for third party access of digital content may include receiving a request to access a digital content object at 210, identifying an amount of assigned units for the digital content object at 220, identifying an amount of available units 230, determining whether to grant the request at 240, responding to the request at 250, or a combination thereof.
In some embodiments, a request to access content may be received at 210. For example, a provider, such as the provider 120 shown in
In some embodiments, the request may indicate a selected digital content object. In some embodiments, the request to access content may include information identifying the customer, such as account information associated with the customer system, and may include information identifying the third party, such as an identifier of the third party device 150 shown in
In some embodiments, assigned license units for the selected digital content may be identified at 220. In some embodiments, the number of assigned units for a digital content object may remain constant or may vary over time. In some embodiments, a license manager, such as the license manager 140 shown in
In some embodiments, a number or cardinality of available units associated with the customer system may be determined at 230. The available units may indicate a number of licensing units that may be used by the customer system at a given time, such as at the time the request is received. For example, although not shown in
In some embodiments, subgroups may be identified within the customer system and a portion of the available units associated with the customer system may be allocated to each respective subgroup. For example, the nodes 162/164 shown in
In some embodiments, whether to grant access may be determined at 240. For example, determining whether to grant access at 240 may include determining whether the count of available units for the customer or the customer subgroup is equal to or greater than the number of assigned units for the digital content. In some embodiments, available units may be associated with the third party device independently of the customer system and determining whether to grant access at 240 may include determining whether the count of a combination of available units for the customer or the customer subgroup and available units for the third party device is equal to or greater than the number of assigned units for the digital content.
In some embodiments, a response may be output at 250. For example, the provider or licensing manager may generate a response indicating that the request for access is granted or denied and may transmit the response to the third party device, the customer system, or both.
In some embodiments, the request for access may be denied. For example, the number of available units associated with the customer or the customer subgroup may be less than the number of assigned units for the requested digital content and the request may be denied. In some embodiments, the provider may reject the request and may prevent the customer system, the third party device, or both, from accessing to the content.
In some embodiments, the request for access may be granted. For example, the number of available units associated with the customer or the customer subgroup may be equal to or greater than the number of assigned units for the requested digital content and the request may be granted.
Although not shown separately, in some embodiments, granting the request may include charging, redeeming, or exchanging a number of available licensing units allocated to the customer system or the customer subgroup corresponding to the number of assigned units for the digital content object. For example, the license manager or provider may record the number of licensing units charged, may update the number available units associated with the customer system or the customer subgroup, or both. In some embodiments, the license manager or provider may record any change in charged units or available units in a log. In some embodiments, the number of available units for the customer system or the customer subgroup may be decreased in an amount equal to the number of assigned units for the digital content indicated in the request.
In some embodiments, granting the request may include determining whether to charge one or more of the available licensing units allocated to the customer system or the customer subgroup. For example, the provider or the licensing manager may determine the number of checked out units currently charged against the customer system or the customer subgroup, and may determine a number of licensing units to charge against the customer system or the customer subgroup based on a difference between the number of assigned units for the requested content and the number of currently checked out units for the customer or the customer subgroup. For example, the number of currently checked out units for the customer or the customer subgroup may be greater than the number of assigned units and granting the request may omit checking out available units. In another example, the number of currently checked out units for the customer or the customer subgroup may be less than the number of assigned units and granting the request may include checking out a number of available units equal to the difference between the number of assigned units and the number of currently checked out units.
Although not shown separately, in some embodiments, the third party device may access the digital content in response to receiving a response granting the request. For example, the third party device may receive the requested content from the provider via the customer system. In some embodiments, the available units for the customer or the customer subgroup may be updated in response to the third party device accessing the content.
Although not shown separately, in some embodiments, the number of charged units may be returned to the customer system or the customer subgroup upon completion or termination of the access of the digital content.
In some embodiments, accessing digital content using unit-based licensing by a third party may include identifying a digital content object at 310, generating a request to access the digital content object at 320, transmitting the request to access the digital content object at 330, receiving a response to the request at 340, accessing the digital content object at 350, or a combination thereof.
In some embodiments, a digital content object may be identified at 310. For example, identifying the digital content object may include identifying a computer software program, video game, music, a movie, a video, or any other media that may be embodied in digital form, and may be accessed, downloaded, input, or otherwise transferred to a computer or processor. In some embodiments, identifying a digital content object may include identifying a plurality of digital content objects.
In some embodiments, a request to access the identified digital content object may be generated at 320. In some embodiments, the request may indicate the digital content object identified at 310. In some embodiments, the request to access content may include information identifying the customer, such as account information associated with the customer system, and may include information identifying the third party, such as an identifier of the third party device 150 shown in
In some embodiments, a request to access the identified digital content object may be transmitted at 330. For example, a third party, such as the third party device 150 shown in
In some embodiments, a response to the request may be received at 340. For example, the provider or licensing manager may generate a response indicating that the request for access is granted or denied and may transmit the response to the third party device, the customer system, or both.
In some embodiments, the response may indicate whether the request is granted or denied. In some embodiments, whether the request is granted or denied may depend on a count or cardinality of assigned license units for the selected digital content. In some embodiments, the number of assigned units for a digital content object may remain constant or may vary over time. In some embodiments, a license manager, such as the license manager 140 shown in
In some embodiments, whether the request is granted or denied may depend on a count or cardinality of available licensing units associated with the customer system. The available units may indicate a number of licensing units that may be used by the customer system at a given time, such as at the time the request is received. For example, although not shown in
In some embodiments, subgroups may be identified within the customer system and a portion of the available units associated with the customer system may be allocated to each respective subgroup. For example, the nodes 162/164 shown in
In some embodiments, whether the request is granted or denied may be based on whether the count, or cardinality, of available units for the customer or the customer subgroup is equal to or greater than the number, or cardinality, of assigned units for the digital content, which may indicated that the cardinality of assigned units for the digital content is within, such as equal to or less than, the cardinality of available units for the customer or the customer subgroup or may indicate that the cardinality of assigned units for the digital content exceeds the cardinality of available units for the customer or the customer subgroup. In some embodiments, available units may be associated with the third party device independently of the customer system and whether the request is granted or denied may depend on whether the count of a combination of available units for the customer or the customer subgroup and available units for the third party device is equal to or greater than the number of assigned units for the digital content.
In some embodiments, the request for access may be denied. For example, the number of available units associated with the customer or the customer subgroup may be less than the number of assigned units for the requested digital content and the request may be denied. In some embodiments, the provider may reject the request and may prevent the customer system, the third party device, or both, from accessing to the content.
In some embodiments, the request for access may be granted. For example, the number of available units associated with the customer or the customer subgroup may be equal to or greater than the number of assigned units for the requested digital content and the request may be granted.
Although not shown separately, in some embodiments, granting the request may include charging, redeeming, or exchanging a number of available licensing units allocated to the customer system or the customer subgroup corresponding to the number of assigned units for the digital content object. For example, the license manager or provider may record the number of licensing units charged, may update the number available units associated with the customer system or the customer subgroup, or both. In some embodiments, the license manager or provider may record any change in charged units or available units in a log. In some embodiments, the number of available units for the customer system or the customer subgroup may be decreased in an amount equal to the number of assigned units for the digital content indicated in the request.
In some embodiments, granting the request may include determining whether to charge one or more of the available licensing units allocated to the customer system or the customer subgroup. For example, the provider or the licensing manager may determine the number of checked out units currently charged against the customer system or the customer subgroup, and may determine a number of licensing units to charge against the customer system or the customer subgroup based on a difference between the number of assigned units for the requested content and the number of currently checked out units for the customer or the customer subgroup. For example, the number of currently checked out units for the customer or the customer subgroup may be greater than the number of assigned units and granting the request may omit checking out available units. In another example, the number of currently checked out units for the customer or the customer subgroup may be less than the number of assigned units and granting the request may include checking out a number of available units equal to the difference between the number of assigned units and the number of currently checked out units.
In some embodiments, the third party device may access the digital content in response to receiving a response granting the request at 350. For example, the third party device may receive the requested content from the provider via the customer system. In some embodiments, the available units for the customer or the customer subgroup may be updated in response to the third party device accessing the content.
Although not shown separately, in some embodiments, the number of charged units may be returned to the customer system or the customer subgroup upon completion or termination of the access of the digital content.
While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiments but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims, which scope is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures as is permitted under the law.
This application claims priority to U.S. Provisional Patent Application No. 61/985,265, filed on Apr. 28, 2014, which is incorporated by reference in its entirety herein.
Number | Name | Date | Kind |
---|---|---|---|
4754426 | Rast et al. | Jun 1988 | A |
4937863 | Robert et al. | Jun 1990 | A |
5204897 | Wyman | Apr 1993 | A |
5260999 | Wyman | Nov 1993 | A |
5390297 | Barber et al. | Feb 1995 | A |
5438508 | Wyman | Aug 1995 | A |
5579222 | Bains et al. | Nov 1996 | A |
5606493 | Duscher et al. | Feb 1997 | A |
5634080 | Kikinis et al. | May 1997 | A |
5671412 | Christiano | Sep 1997 | A |
5742813 | Kavanagh et al. | Apr 1998 | A |
5745879 | Wyman | Apr 1998 | A |
5752041 | Fosdick | May 1998 | A |
5758069 | Olsen | May 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5790664 | Coley | Aug 1998 | A |
5835910 | Kavanagh et al. | Nov 1998 | A |
5905860 | Olsen | May 1999 | A |
5920861 | Hall | Jul 1999 | A |
5931901 | Wolfe et al. | Aug 1999 | A |
5966444 | Yuan et al. | Oct 1999 | A |
5973683 | Cragun et al. | Oct 1999 | A |
5990883 | Byrne et al. | Nov 1999 | A |
6009401 | Horstmann | Dec 1999 | A |
6020883 | Herz et al. | Feb 2000 | A |
6026387 | Kesel | Feb 2000 | A |
6029176 | Cannon | Feb 2000 | A |
6038591 | Wolfe et al. | Mar 2000 | A |
6049332 | Boetje et al. | Apr 2000 | A |
6049789 | Frison et al. | Apr 2000 | A |
6088722 | Herz et al. | Jul 2000 | A |
6101606 | Diersch | Aug 2000 | A |
6118492 | Milnes et al. | Sep 2000 | A |
6133909 | Schein et al. | Oct 2000 | A |
6141754 | Choy | Oct 2000 | A |
6160570 | Sitnik | Dec 2000 | A |
6161137 | Ogdon et al. | Dec 2000 | A |
6161142 | Wolfe et al. | Dec 2000 | A |
6169992 | Beall et al. | Jan 2001 | B1 |
6173269 | Solokl et al. | Jan 2001 | B1 |
6182050 | Ballard | Jan 2001 | B1 |
6198906 | Boetje et al. | Mar 2001 | B1 |
6219652 | Carter et al. | Apr 2001 | B1 |
6240415 | Blumberg | May 2001 | B1 |
6256664 | Donoho et al. | Jul 2001 | B1 |
6262721 | Tsukidate et al. | Jul 2001 | B1 |
6263362 | Donoho et al. | Jul 2001 | B1 |
6263501 | Schein et al. | Jul 2001 | B1 |
6275844 | Rail | Aug 2001 | B1 |
6286140 | Ivanyi | Sep 2001 | B1 |
6317881 | Shah-Nazaroff et al. | Nov 2001 | B1 |
6324519 | Eldering | Nov 2001 | B1 |
6411941 | Mullor et al. | Jun 2002 | B1 |
6473794 | Guheen et al. | Oct 2002 | B1 |
6502079 | Ball | Dec 2002 | B1 |
6502124 | Shimakawa et al. | Dec 2002 | B1 |
6519571 | Guheen et al. | Feb 2003 | B1 |
6536037 | Guheen et al. | Mar 2003 | B1 |
6574612 | Baratti et al. | Jun 2003 | B1 |
6591244 | Jim et al. | Jul 2003 | B2 |
6606744 | Mikurak | Aug 2003 | B1 |
6615166 | Guheen et al. | Sep 2003 | B1 |
6671818 | Mikurak | Dec 2003 | B1 |
6721713 | Guheen et al. | Apr 2004 | B1 |
6732106 | Okamoto et al. | May 2004 | B2 |
6728766 | Cox et al. | Aug 2004 | B2 |
6816882 | Conner et al. | Nov 2004 | B1 |
6859792 | Marjadi et al. | Feb 2005 | B1 |
6889206 | Nuttall | May 2005 | B1 |
6948070 | Ginter | Sep 2005 | B1 |
6957186 | Guheen et al. | Oct 2005 | B1 |
6966832 | Leen et al. | Nov 2005 | B2 |
7013294 | Sekigawa et al. | Mar 2006 | B1 |
7036091 | Nguyen | Apr 2006 | B1 |
7124101 | Mikurak | Oct 2006 | B1 |
7130807 | Mikurak | Oct 2006 | B1 |
7139737 | Takahashi et al. | Nov 2006 | B2 |
7165041 | Guheen et al. | Jan 2007 | B1 |
7194439 | Kassan et al. | Mar 2007 | B2 |
7203966 | Abburi et al. | Apr 2007 | B2 |
7209900 | Hunter et al. | Apr 2007 | B2 |
7225165 | Kyojima | May 2007 | B1 |
7299209 | Collier | Nov 2007 | B2 |
7313512 | Traut et al. | Dec 2007 | B1 |
7315826 | Guheen et al. | Jan 2008 | B1 |
7343365 | Farnham | Mar 2008 | B2 |
7395245 | Okamoto et al. | Jul 2008 | B2 |
7590601 | Shea et al. | Sep 2009 | B2 |
7630986 | Herz | Dec 2009 | B1 |
7672972 | Marjadi | Mar 2010 | B1 |
7716077 | Mikurak | May 2010 | B1 |
7788272 | Ray | Aug 2010 | B2 |
7809648 | Misra | Oct 2010 | B2 |
7818350 | New et al. | Oct 2010 | B2 |
7859551 | Bulman | Dec 2010 | B2 |
8032409 | Mikurak | Oct 2011 | B1 |
8073780 | Marjadi | Dec 2011 | B2 |
8126938 | Cohen | Feb 2012 | B2 |
8340796 | Stefik | Dec 2012 | B2 |
8392505 | Haughay et al. | Mar 2013 | B2 |
8504932 | Quek et al. | Aug 2013 | B2 |
8548839 | Neilesh | Oct 2013 | B2 |
8831998 | Cramer | Sep 2014 | B1 |
8943425 | Wickramasurya et al. | Jan 2015 | B2 |
9065824 | Valdivia | Jun 2015 | B1 |
9135580 | Lyman | Sep 2015 | B1 |
9678637 | Brothers et al. | Jun 2017 | B1 |
9712587 | Alfishawi et al. | Jul 2017 | B1 |
10120983 | Smith, II | Nov 2018 | B2 |
10230673 | Lewis et al. | Mar 2019 | B1 |
20010010046 | Muyres | Jul 2001 | A1 |
20010011253 | Coley | Aug 2001 | A1 |
20010013024 | Takahashi et al. | Aug 2001 | A1 |
20010037404 | Hafsteinsson | Nov 2001 | A1 |
20020007298 | Jim et al. | Jan 2002 | A1 |
20020029347 | Edelman | Mar 2002 | A1 |
20020046181 | Story, Jr. | Apr 2002 | A1 |
20020049679 | Russell et al. | Apr 2002 | A1 |
20020059094 | Hosea et al. | May 2002 | A1 |
20020069263 | Sears et al. | Jun 2002 | A1 |
20020069420 | Russell | Jun 2002 | A1 |
20020091568 | Kraft et al. | Jul 2002 | A1 |
20020120564 | Strietzel | Aug 2002 | A1 |
20020129356 | Hellerstein et al. | Sep 2002 | A1 |
20020156824 | Armstrong | Oct 2002 | A1 |
20020161908 | Benitez | Oct 2002 | A1 |
20020183045 | Emmerson et al. | Dec 2002 | A1 |
20020194589 | Crisofalo et al. | Dec 2002 | A1 |
20030036683 | Kehr et al. | Feb 2003 | A1 |
20030046578 | Brown et al. | Mar 2003 | A1 |
20030050979 | Takahashi | Mar 2003 | A1 |
20030059022 | Nebiker et al. | Mar 2003 | A1 |
20030069766 | Hoffman et al. | Apr 2003 | A1 |
20030084165 | Kjellberg et al. | May 2003 | A1 |
20030135380 | Lehr et al. | Jul 2003 | A1 |
20030135474 | Circenis et al. | Jul 2003 | A1 |
20030144903 | Brechner | Jul 2003 | A1 |
20030149993 | Son | Aug 2003 | A1 |
20030182142 | Valenzuela et al. | Sep 2003 | A1 |
20030208763 | McElhatten et al. | Nov 2003 | A1 |
20040122774 | Studd et al. | Jun 2004 | A1 |
20050033613 | Patullo | Feb 2005 | A1 |
20050049931 | Wisnudel et al. | Mar 2005 | A1 |
20050077349 | Bonalle | Apr 2005 | A1 |
20050182731 | Marjadi et al. | Aug 2005 | A1 |
20060004668 | Hamnen et al. | Jan 2006 | A1 |
20060020556 | Hamnen et al. | Jan 2006 | A1 |
20060073820 | Craswell et al. | Apr 2006 | A1 |
20060106728 | Yellai et al. | May 2006 | A1 |
20060143134 | So et al. | Jun 2006 | A1 |
20060143236 | Wu | Jun 2006 | A1 |
20060153073 | Ghiware | Jul 2006 | A1 |
20060248017 | Koka et al. | Nov 2006 | A1 |
20060259930 | Rothschild | Nov 2006 | A1 |
20060287959 | Blecken | Dec 2006 | A1 |
20060294019 | Dayan et al. | Dec 2006 | A1 |
20070016599 | Plastina | Jan 2007 | A1 |
20070106622 | Boomershine et al. | May 2007 | A1 |
20070219923 | Shea et al. | Sep 2007 | A1 |
20070226150 | Piertrzak et al. | Sep 2007 | A1 |
20070226155 | Yu et al. | Sep 2007 | A1 |
20070233578 | Fusz et al. | Oct 2007 | A1 |
20070233837 | Imai | Oct 2007 | A1 |
20070244826 | Wang | Oct 2007 | A1 |
20070277233 | Bodin et al. | Nov 2007 | A1 |
20070299845 | Tokunago | Dec 2007 | A1 |
20080005032 | Znidarsic | Jan 2008 | A1 |
20080015888 | Dang | Jan 2008 | A1 |
20080064493 | Andersson | Mar 2008 | A1 |
20080071689 | Tabet | Mar 2008 | A1 |
20080080552 | Gates et al. | Apr 2008 | A1 |
20080082450 | Grimm et al. | Apr 2008 | A1 |
20080083025 | Meijer et al. | Apr 2008 | A1 |
20080154798 | Valz | Jun 2008 | A1 |
20080178284 | Harwell | Jul 2008 | A1 |
20080208692 | Garaventi | Aug 2008 | A1 |
20080228533 | McGuire et al. | Sep 2008 | A1 |
20080228689 | Tewary et al. | Sep 2008 | A1 |
20080235116 | Jensen | Sep 2008 | A1 |
20080250349 | Peiro et al. | Oct 2008 | A1 |
20080288542 | Buttars | Nov 2008 | A1 |
20080319910 | Duffus et al. | Dec 2008 | A1 |
20090003712 | Mei et al. | Jan 2009 | A1 |
20090048860 | Brotman et al. | Feb 2009 | A1 |
20090094159 | Cunningham | Apr 2009 | A1 |
20090132435 | Titus et al. | May 2009 | A1 |
20090150343 | English | Jun 2009 | A1 |
20090240629 | Xie et al. | Sep 2009 | A1 |
20090287513 | Anderson | Nov 2009 | A1 |
20090319638 | Faith | Dec 2009 | A1 |
20090327437 | Estrada | Dec 2009 | A1 |
20100017725 | McCarthy et al. | Jan 2010 | A1 |
20100114531 | Korn | May 2010 | A1 |
20100185656 | Pollard | Jul 2010 | A1 |
20100186066 | Pollard | Jul 2010 | A1 |
20100217613 | Kelly | Aug 2010 | A1 |
20100223677 | Scapa | Sep 2010 | A1 |
20100228679 | Scapa | Sep 2010 | A1 |
20100251181 | Lal | Sep 2010 | A1 |
20100278453 | King | Nov 2010 | A1 |
20110047566 | Matuchniak | Feb 2011 | A1 |
20110113133 | Kelly | May 2011 | A1 |
20110213681 | Shahid | Sep 2011 | A1 |
20110239131 | Koren | Sep 2011 | A1 |
20120022954 | Garcia et al. | Jan 2012 | A1 |
20120041812 | Postrel | Feb 2012 | A1 |
20120066089 | Henderson | Mar 2012 | A1 |
20120173975 | Herz et al. | Jul 2012 | A1 |
20120185389 | Ross | Jul 2012 | A1 |
20120226978 | Harberts et al. | Sep 2012 | A1 |
20120246734 | Pride et al. | Sep 2012 | A1 |
20120251080 | Svendsen | Oct 2012 | A1 |
20120272185 | Dodson | Oct 2012 | A1 |
20120272256 | Bedi | Oct 2012 | A1 |
20120296681 | Fitzgerald | Nov 2012 | A1 |
20120317198 | Patton | Dec 2012 | A1 |
20130042262 | Riethmueller | Feb 2013 | A1 |
20130054279 | Sharp | Feb 2013 | A1 |
20130138426 | DelRocco | May 2013 | A1 |
20130145385 | Aghajanyan et al. | Jun 2013 | A1 |
20130166649 | Atzmon | Jun 2013 | A1 |
20130179680 | Peterka et al. | Jul 2013 | A1 |
20130185656 | Heikes et al. | Jul 2013 | A1 |
20130246916 | Reimann et al. | Sep 2013 | A1 |
20130311768 | Fosmark | Nov 2013 | A1 |
20130312022 | Yoon | Nov 2013 | A1 |
20130332395 | Kim et al. | Dec 2013 | A1 |
20130339362 | Yang | Dec 2013 | A1 |
20130339397 | Herasymchuk | Dec 2013 | A1 |
20140208391 | Farnsworth | Jul 2014 | A1 |
20140222775 | Zohar et al. | Aug 2014 | A1 |
20140258029 | Thierry | Sep 2014 | A1 |
20140278968 | Strompolos | Sep 2014 | A1 |
20140280079 | Jain | Sep 2014 | A1 |
20140280899 | Brewster, Jr. | Sep 2014 | A1 |
20140372315 | Faith | Dec 2014 | A1 |
20140379705 | Zureiqat | Dec 2014 | A1 |
20140379729 | Savage | Dec 2014 | A1 |
20150051925 | Yudin | Feb 2015 | A1 |
20150074413 | Hao | Mar 2015 | A1 |
20150088668 | Bruce | Mar 2015 | A1 |
20150117631 | Tuchman | Apr 2015 | A1 |
20150120357 | Tuchman | Apr 2015 | A1 |
20150193600 | Matsuda | Jul 2015 | A1 |
20150302321 | Scapa et al. | Oct 2015 | A1 |
20150310354 | Mahalingam et al. | Oct 2015 | A1 |
20150310513 | Fariello et al. | Oct 2015 | A1 |
20150346928 | MacArthur | Dec 2015 | A1 |
20150379118 | Wickenkamp | Dec 2015 | A1 |
20160057473 | Mitchell | Feb 2016 | A1 |
20160092780 | Kelley | Mar 2016 | A1 |
20160253710 | Publicover | Sep 2016 | A1 |
20160297398 | Jefferies | Oct 2016 | A1 |
20160359816 | Vedula et al. | Dec 2016 | A1 |
20170295119 | Rosenberg | Oct 2017 | A1 |
20170300456 | Rimmer | Oct 2017 | A1 |
20170339081 | Beust | Nov 2017 | A1 |
20180046944 | Barbera | Feb 2018 | A1 |
20180124105 | Rodrigues | May 2018 | A1 |
20180349641 | Barday | Dec 2018 | A1 |
20190215344 | Barday | Jul 2019 | A1 |
20190222476 | McEntee | Jul 2019 | A1 |
20190332803 | Barday | Oct 2019 | A1 |
Number | Date | Country |
---|---|---|
102356397 | Feb 2012 | CN |
1862202 | May 2007 | EP |
2409258 | Jan 2012 | EP |
2414954 | Feb 2012 | EP |
2002091595 | Mar 2002 | JP |
2005250635 | Sep 2005 | JP |
2007265193 | Oct 2007 | JP |
20070286703 | Nov 2007 | JP |
20010095908 | Nov 2001 | KR |
101185968 | Sep 2012 | KR |
9220021 | Nov 1992 | WO |
2010108006 | Jan 2011 | WO |
2010115107 | Jan 2011 | WO |
WO 2012048086 | Apr 2012 | WO |
Entry |
---|
Keoh, “Marlin: Toward Seamless Content Sharing and Rights Management,” IEEE, all pages. (Year: 2011). |
Altair Releases HyperWorks 9.0, Connecting Engineerings with New Solver Technology and to the Global Grid: Newest version of Altair's simulation platform delivers on-demand access to the ISV applications and offers multi-core licensing business model Anonymous. PR Newswire [New York] May 19, 2008, downloaded from ProQuestDirect on the Internet 06, 3 pages. |
Brignall, “Peugeot launches car club with a difference”, The Guardian, Jul. 9, 2010, retrieved from: http://www.guardian.co.uk/money/2010/jul/10/peugeot-car-club-mu/print on Oct. 4, 2011. |
Levine, “Share My Ride”, The New York Times, Mar. 8, 2009, retrieved from: http://www.nytimes.com/2009/03/08/magazine/08Zipcar-t.html?pagewanted=print on Oct. 4, 2011. |
Zipcar, “is zipcar for me”, retrieved from: http://www.zipcar.com/is-it/ on Oct. 4, 2011. |
Zipcar, “rates & plans”, retrieved from: http://www.zipcar.com/atlanta/check-rates on Oct. 4, 2011. |
Notification of Transmittal dated Dec. 27, 2012, the International Search Report and the Written Opinion of the International Searching Authority (ISA/KR) from corresponding International Application No. PCT/US2011/055060 filed Oct. 6, 2011. |
Notification of Transmittal, International Preliminary Report on Patentability dated Sep. 29, 2011 from the corresponding International Patent Application No. PCT/US2010/027820 filed Mar. 18, 2010. |
Notification of Transmittal, International Search Report and Written Opinion dated Oct. 26, 2010 from the corresponding International Patent Application No. PCT/US2010/027820 filed Mar. 18, 2010. |
Extended European Search Report in co-pending European Application No. 10754111.2 dated Aug. 14, 2012 in 5 pages. |
Notification of Transmittal, International Preliminary Report on Patentability dated Oct. 13, 2011 from the corresponding International Patent Application No. PCT/US2010/029787 filed Apr. 2, 2010. |
Notification of Transmittal, International Search Report and Written Opinion dated Nov. 2, 2010 from the corresponding International Patent Application No. PCT/US2010/029787 filed Apr. 2, 2010. |
EP Suppl Search Report for EP App No. 10759478.0 dated Apr. 18, 2013 (5 pages). |
JP Office Action for JP 2012-503741 dated Jan. 20, 2014 (4 pages). |
Final Office Action in Appin. No. 14/531,443, dated Mar. 21, 2019, 15 pages. |
Number | Date | Country | |
---|---|---|---|
20150310354 A1 | Oct 2015 | US |
Number | Date | Country | |
---|---|---|---|
61985265 | Apr 2014 | US |