IP Library › Granted Patent US 12,519,780
Granted Patent B2
US 12,519,780 · App. 18/407,659 · Granted Jan 6, 2026

Login based features

Inventors: Laxminarayana Dalimba (Bengaluru, IN); Himanshu Jain (Bengaluru, IN)
Assignee: DISH Network Techonlogies India Private Limited
H04L63/083
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,519,780
App. No.
18/407,659
Granted
Jan 6, 2026
Kind
B2
Abstract

A system includes a fixed device, an account management system (“AMS”) server, a property management system (“PMS”) server, a personal user device, and a content server. The PMS server associate the fixed device with a given user. The fixed device, when executing computer instructions for a presence application, perform presence operations including receiving a 1 st user code from the PMS server, receiving a 1 st user access code from the AMS server, and communicating the 1 st user access code as a 2 nd user access code to the PUD. The AMS servers uses the 2 nd user access code to verify the PUD can access data stored by the AMS server and the content server uses the 2 nd user access code to validate a request, from the PUD, to receive content from the content server. Processes, devices, computer readable mediums are also described.

Claims (101)

1 . A system comprising:

a fixed device;

an account management system (“AMS”) server coupled to the fixed device;

a property management system (“PMS”) server coupled to the fixed device and the AMS server;

wherein the PMS server associates, at a given time, the fixed device with a given user;

a personal user device (“PUD”) coupled to the AMS server and the fixed device; and

a content server coupled to the fixed device, the AMS server and the PUD;

wherein the fixed device comprises:

a fixed device processor; and

a non-transitory fixed device data store, coupled to the fixed device processor, storing first computer instructions which, when executed by the fixed device processor, instantiate a presence application; and

wherein the presence application configured the fixed device to perform presence operations including:

receiving a 1 st user code from the PMS server;

receiving a 1 st user access code from the AMS server; and

communicating the 1 st user access code as a 2 nd user access code to the PUD; and

wherein the 2 nd user access code is utilized by the AMS server to verify the PUD can access data stored by the AMS server;

wherein the content server receives the 2 nd user access code from the PUD;

wherein the content server verifies the 1 st user access code against a 2 nd user access code;

wherein the content server grants the PUD access to at least one content when a result of the verifying of the 1 st user access code against the 2 nd user access code yields a positive result; and

wherein the 2 nd user access code is utilized by the content server to validate a request, from the PUD, to receive content from the content server.

2 . The system of claim 1 ,

wherein the presence operations further comprise:

communicating a 2 nd user code to the AMS server;

wherein the AMS server receives the 1 st user code from the PMS server; and

wherein the 1 st user code and the 2 nd user code are utilized by the AMS server to verify the fixed device can execute one or more content operations including providing at least one of content control activity data and content preference data to the AMS server for storage by the AMS server.

3 . The system of claim 2 ,

wherein the PMS server associates the 1 st user code with log-in information for the given user.

4 . The system of claim 3 ,

wherein the 1 st user code does not contain the log-in information.

5 . The system of claim 4 ,

wherein the PMS server independently communicates the 1 st user code to the AMS server;

wherein the presence operations further comprise:

receiving, in a combined data transmission, the 1 st user code and the 1 st user access code from the AMS server; and

wherein the AMS server comprises:

an AMS processor executing non-transitory computer instructions, which instantiate an AMS app which performs AMS operations including:

comparing the 1 st user code against the 2 nd user code; and

verifying the fixed device when a result of the comparing of the 1 st user code against the 2 nd user code indicates that operative data in the 1 st user code matches operative data in the 2 nd user code.

6 . The system of claim 5 ,

wherein the AMS operations further comprise:

receiving content control activity data from the fixed device at the given time; and

associating the content control activity data with the 1 st user access code.

7 . The system of claim 6 ,

wherein the AMS operations further comprise:

receiving content preference data from the fixed device at the given time; and

associating the content preference data with the 1 st user access code.

8 . The system of claim 7 ,

wherein the AMS operations further comprise:

verifying the 2 nd user access code against the 1 st user access code; and

when verified, allowing the PUD to access one or more of content control activity data and the content preference data.

9 . An account management system (“AMS”) server comprising:

an AMS processor; and

a non-transitory AMS data store, coupled to the AMS processor, storing non-transitory computer instructions which, when executed by the AMS processor, instantiates an AMS application that performs AMS operations comprising:

receiving a 1 st user code independently communicated by a property management system (“PMS”) server to the AMS;

generating a user access code;

communicating, in a combined data transmission, the 1 st user code and a 1 st user access code to a fixed device coupled to the AMS server;

receiving a 2 nd user access code from a personal user device (“PUD”) coupled to the fixed device and the AMS server;

wherein the 1 st user access code has been previously provided by the fixed device, as the 2 nd user access code, to the PUD;

comparing the 1 st user access code with the 2 nd user access code; and

verifying the PUD can access data stored by the AMS server when the 1 st user access code and the 2 nd user access code contain identical operative data.

10 . The AMS server of claim 9 ,

wherein the data stored by the AMS server includes content control activity data corresponding to one or more interactions by a given user of the fixed device; and

wherein the content control activity data has been previously communicated by the fixed device to the AMS server in at least one data packet that includes the 1 st user access code.

11 . The AMS Server of claim 10 ,

wherein the content control activity data includes data indicative of at least one trick-play operation previously requested by the given user of the fixed device.

12 . The AMS server of claim 9 ,

wherein the data stored by the AMS server includes content preference data corresponding to one or more preferences for a given user of the fixed device; and

wherein the content preference data has been previously determined by at least one of the fixed device and AMS server based on previous preference indications by the given user.

13 . The AMS server of claim 9 ,

wherein the AMS operations further comprise:

communicating the 1 st user access code to a content server;

wherein the content server verifies the 1 st user access code against a 2 nd user access code received from the PUD; and

wherein the content server grants the PUD access to at least one content when a result of the verifying of the 1 st user access code against the 2 nd user access code yields a positive result.

14 . The AMS server of claim 9 ,

wherein the data stored by the AMS server includes content control activity data received from the fixed device; and

wherein the 2 nd user access code is associated by the AMS server with the content control activity data.

15 . The AMS server of claim 14 ,

wherein the content control activity data identifies at least one trick-play operation initiated by the given user and with respect to a given content and enables the PUD to release the trick-play operation and resume presentation of the given content on the PUD.

16 . The AMS server of claim 15 ,

wherein the trick-play operation is a pause in a presentation of the given content on the fixed device; and

wherein the release of the trick-play operation is a resumption of the presentation of the given content one at least one of the fixed device and the PUD.

17 . The AMS server of claim 9 ,

wherein the data stored by the AMS server includes content preference data generated by the AMS server based on content requested by the fixed device from the content server; and

wherein the 2 nd user access code is associated by the AMS server with the content preference data.

18 . The AMS server of claim 17 ,

wherein the content preference data limits content the PUD can receive from the content server by at least one of content rating, genre, and subject matter.

19 . A non-transitory computer readable medium, having stored thereon computer instructions which, when executed by a processor of an account management system (“AMS”) server, causes the AMS server to perform operations comprising:

generating a user access code;

communicating a 1 st user access code to a fixed device coupled to the AMS server;

receiving a 2 nd user access code from a personal user device (“PUD”) coupled to the fixed device and the AMS server;

wherein the 1 st user access code has been previously provided by the fixed device, as the 2 nd user access code, to the PUD;

verifying the PUD can access data stored by the AMS server when the 1 st user access code and the 2 nd user access code contain identical operative data; and

communicating the 1 st user access code to a content server;

wherein the content server verifies the 1 st user access code against a 2 nd user access code received from the PUD; and

wherein the content server grants the PUD access to at least one content when a result of the verifying of the 1 st user access code against the 2 nd user access code yields a positive result.

20 . The non-transitory computer readable medium of claim 19 ,

wherein the data stored by the AMS server includes content control activity data received from the fixed device;

wherein the 2 nd user access code is associated by the AMS server with the content control activity data;

wherein the content control activity data includes data indicative of at least one trick-play operation previously requested by a given user of the fixed device;

wherein the trick-play operation is a pause in a presentation of a given content on the fixed device;

wherein a release of the trick-play operation is a resumption of the presentation of the given content one at least one of the fixed device and the PUD;

wherein the data stored by the AMS server further includes content preference data corresponding to one or more preferences for a given user of the fixed device; and

wherein the content preference data has been previously determined by at least one of the fixed device and AMS server based on previous preference indications by the given user.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: DALIMBA, LAXMINARAYANA; JAIN, HIMANSHU
To: DISH NETWORK TECHNOLOGIES INDIA PRIVATE LIMITED
Reel/Frame 066063/0818 →
Continuity (1)
Related Publication 20250227103A1 · Jul 10, 2025
References Cited (87)
US 6054950A · Fontana · 2000 [cited by applicant]
US 6571221B1 · Stewart et al. · 2003 [cited by applicant]
US 7231516B1 · Sparrell et al. · 2007 [cited by applicant]
US 7372821B2 · Sato et al. · 2008 [cited by applicant]
US 8108493B2 · Lakamp · 2012 [cited by applicant]
US 8495729B2 · Park · 2013 [cited by applicant]
US 8621530B1 · Guzman et al. · 2013 [cited by applicant]
US 8856843B1 · Hubach et al. · 2014 [cited by applicant]
US 8903980B2 · Hyvarinen et al. · 2014 [cited by applicant]
US 9215139B2 · Hyvarinen et al. · 2015 [cited by applicant]
US 9326139B2 · Johan · 2016 [cited by applicant]
US 9330250B2 · Medvinsky et al. · 2016 [cited by applicant]
US 9532097B1 · Chen et al. · 2016 [cited by applicant]
US 10291956B2 · Zdepski et al. · 2019 [cited by applicant]
US 10327035B2 · Zerr et al. · 2019 [cited by applicant]
US 10631042B2 · Zerr et al. · 2020 [cited by applicant]
US 10743075B2 · Zerr et al. · 2020 [cited by applicant]
US 10996702B2 · Imes et al. · 2021 [cited by applicant]
US 11330326B2 · Zerr et al. · 2022 [cited by applicant]
US 11671651B2 · Zerr et al. · 2023 [cited by applicant]
US 11770197B2 · Zhang et al. · 2023 [cited by applicant]
US 12184439B2 · Ergen · 2024 [cited by applicant]
US 20030061315A1 · Jin · 2003 [cited by applicant]
US 20050283791A1 · McCarthy et al. · 2005 [cited by applicant]
US 20060281477A1 · Downes · 2006 [cited by applicant]
US 20070088814A1 · Torii · 2007 [cited by applicant]
US 20080004075A1 · Horton et al. · 2008 [cited by applicant]
US 20080095374A1 · Schreyer · 2008 [cited by applicant]
US 20100128709A1 · Liu et al. · 2010 [cited by applicant]
US 20100180312A1 · Toya · 2010 [cited by applicant]
US 20110116419A1 · Cholas et al. · 2011 [cited by applicant]
US 20110314192A1 · Ahn et al. · 2011 [cited by applicant]
US 20120151510A1 · Ramaswamy et al. · 2012 [cited by applicant]
US 20120210011A1 · Liu et al. · 2012 [cited by applicant]
US 20120259967A1 · Hyvarinen et al. · 2012 [cited by applicant]
US 20130111522A1 · Tatem et al. · 2013 [cited by applicant]
US 20130258197A1 · Schmehl et al. · 2013 [cited by applicant]
US 20130346564A1 · Warrick et al. · 2013 [cited by applicant]
US 20140033236A1 · Guzman et al. · 2014 [cited by applicant]
US 20140337927A1 · Medvinsky et al. · 2014 [cited by applicant]
US 20150051994A1 · Ward et al. · 2015 [cited by applicant]
US 20150324332A1 · Perret et al. · 2015 [cited by applicant]
US 20160080821A1 · Makhijani et al. · 2016 [cited by applicant]
US 20160099928A1 · Chatwin et al. · 2016 [cited by applicant]
US 20160227408A1 · Sherin · 2016 [cited by applicant]
US 20170094345A1 · Zerr et al. · 2017 [cited by applicant]
US 20180095121A1 · Gilson et al. · 2018 [cited by applicant]
US 20180343397A1 · Chandrashekar et al. · 2018 [cited by applicant]
US 20190364120A1 · Bandela et al. · 2019 [cited by applicant]
US 20210203498A1 · Shin · 2021 [cited by examiner]
US 20220021684A1 · Mensah · 2022 [cited by examiner]
US 20220137204A1 · Nguyen et al. · 2022 [cited by applicant]
US 20220148217A1 · Hallett et al. · 2022 [cited by applicant]
US 20220284624A1 · Nimmagadda et al. · 2022 [cited by applicant]
US 20230116882A1 · Bates et al. · 2023 [cited by applicant]
US 20230222674A1 · Balarajashetty et al. · 2023 [cited by applicant]
US 20230269420A1 · Zerr et al. · 2023 [cited by applicant]
US 20230394951A1 · Jeong et al. · 2023 [cited by applicant]
US 20240121129A1 · Ergen et al. · 2024 [cited by applicant]
US 20240305496A1 · Ergen et al. · 2024 [cited by applicant]
US 20240346274A1 · DiTullio · 2024 [cited by examiner]
US 20250039860A1 · Reddy et al. · 2025 [cited by applicant]
US 20250088822A1 · McClellan · 2025 [cited by applicant]
U.S. Appl. No. 17/960,185, filed Oct. 5, 2022. [cited by applicant]
U.S. Appl. No. 18/669,902, filed May 21, 2024. [cited by applicant]
U.S. Appl. No. 18/626,211, filed Apr. 3, 2024. [cited by applicant]
U.S. Appl. No. 18/885,679, filed Sep. 15, 2024. [cited by applicant]
Fan, J. I., and K. Khoshelham. “Augmented Reality Asset Tracking Using Hololens.” ISPRS Annals of the Photogrammetry, RemoteSensing and Spatial Information Sciences 4 (2021): 121-127. (Year: 2021). [cited by applicant]
U.S. Appl. No. 17/960,185, Prosecution History through Oct. 26, 2024. [cited by applicant]
Veluchandhar, V., and K. Kandavel. “WATS-SNADSC: A Wireless Asset Tracking System using Sensor Networks with Auto DetectSpy Camera in Forensic Science.” J. Sci 1.4 (2008): 178-185. (Year: 2008). [cited by applicant]
U.S. Appl. No. 17/575,497, filed Jan. 13, 2022. [cited by applicant]
U.S. Appl. No. 18/669,902, Notice of Allowance, Feb. 27, 2025 (available at USPTO Patent Center). [cited by applicant]
U.S. Appl. No. 17/575,497, Final Office Action, Sep. 28, 2024 (available at Patent Center). [cited by applicant]
U.S. Appl. No. 17/960,185, Prosecution History through May 21, 2024 (available at Patent Center). [cited by applicant]
U.S. Appl. No. 18/626,211, Prosecution History through May 21, 2024 (available at Patent Center). [cited by applicant]
U.S. Appl. No. 17/960,185, Non-final Office Action, dated Dec. 12, 2024 (available at USPTO Patent Center). [cited by applicant]
U.S. Appl. No. 17/960,185, Response to Non-final Office Action with electronic Terminal Disclaimer, dated Dec. 12, 2024 (available at USPTO Patent Center). [cited by applicant]
“Ultra-Wideband RTLS, Positioning, & Sensor Technology”, Inpixon.com, web page downloaded from the Internet at https://www.inpixon.com/technology/standards/ultra-wideband, on Jun. 9, 2024. [cited by applicant]
U.S. Appl. No. 18/885,679, filed Sep. 15, 2024 (Available at USPTO Patent Center). [cited by applicant]
U.S. Appl. No. 17/575,497, Prosecution History through Sep. 15, 2024 (available at Patent Center). [cited by applicant]
U.S. Appl. No. 17/960,185, Prosecution History through Sep. 15, 2024 (available at Patent Center). [cited by applicant]
U.S. Appl. No. 18/626,211, Prosecution History through Sep. 15, 2024 (available at Patent Center). [cited by applicant]
Wikipedia, “Indoor Positioning System”, downloaded from the Internet on Oct. 19, 2021 at https://en.wikipedia.org/wiki/Indoor_positioning_system. [cited by applicant]
Wikipedia, definition of “AirTag”, downloaded from the Internet onOct. 19, 2021 from https://en.wikipedia.org/wiki/airtag. [cited by applicant]
U.S. Appl. No. 18/885,679, Non-final Office Action, Jul. 29, 2025 (Available at USPTO Patent Center). [cited by applicant]
U.S. Appl. No. 18/885,679, Non-final Office Action, Oct. 3, 2025 (Available at USPTO Patent Center). [cited by applicant]
U.S. Appl. No. 18/626,211, Response to non-final Office Action, Oct. 15, 2025 (available at Patent Center). [cited by applicant]