IP Library Granted Patent US 8,832,676
Granted Patent B2
US 8,832,676 · App. 12/885,133 · Granted Sep 9, 2014

Apparatuses, methods and systems for a social networking application updater

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 8,832,676
App. No.
12/885,133
Granted
Sep 9, 2014
Kind
B2
Abstract

The APPARATUSES, METHODS AND SYSTEM FOR A SOCIAL NETWORKING APPLICATION UPDATER provide live reconciliation of code updates to multi-user social networking applications in highly dynamic build environments (“SNAM”). In one embodiment, an application updating processor-implemented method is disclosed. In this embodiment, the SNAM obtains a module dependency graph for a current version of an application. It identifies current module version numbers for one or more modules in the module dependency graph for the current version of the application. The SNAM obtains, for the modules in the module dependency graph, module version numbers for updated module versions. It analyzes compatibility specifications for the current version of the application and the updated module versions; The SNAM determines that the updated version of the application can be generated based on the analysis. It obtains an updated module version for one of the modules in the module dependency graph of the current version of the application; and generates the updated version of the application using the obtained updated module version.

Claims (77)

1. A processor-implemented application updating method, comprising:

obtaining an indication to check whether to generate an updated version of an application;

obtaining a module dependency graph for a current version of the application;

identifying current module version numbers for one or more modules in the module dependency graph for the current version of the application;

obtaining, for the modules in the module dependency graph, module version numbers for updated module versions stored in a code database;

obtaining compatibility specifications for the current version of the application and the updated module versions stored in the code database;

analyzing, via a processor, the compatibility specifications for the current version of the application and the updated module versions;

determining that the updated version of the application can be generated using the updated module versions stored in the code database, based on analyzing the compatibility specifications for the current version of the application and the updated module versions and based on updates available within the updated module versions for the application; and

generating the updated version of the application using the updated module versions stored in the code database, the generation of the updated version causing transfer of a user from the current version of the application to the updated version of the application and dynamically establishing access for the user to the updated version, wherein the transfer of the user is performed in real-time while the user is utilizing the application, wherein dynamically establishing access includes loading a state associated with the user for the current version of the application prior to the transfer, into the updated version of the application.

2. The method of claim 1 , further comprising:

obtaining an updated module version for one of the modules in the module dependency graph of the current version of the application; and

generating the updated version of the application using the obtained updated module version.

3. The method of claim 1 , wherein identifying the current module version numbers for the one or more modules in the module dependency graph for the current version of the application includes:

obtaining the current version of the application;

parsing the obtained current version of the application; and

determining the module dependency graph of the current version of the application based on parsing the current version of the application.

4. The method of claim 1 , wherein the application is a multi-user social networking application.

5. The method of claim 1 , wherein the compatibility specifications include information on at least one of: hardware requirements; operating system requirements; and web browser requirements.

6. The method of claim 2 , further comprising:

providing a notification for a user of the generated updated version of the application;

obtaining an indication to provide the updated version of the application for the user; and

providing the updated version of the application for the user.

7. The method of claim 6 , further comprising:

obtaining an indication that the updated version of the application replaced the current version of the application on a user device as the user was using the application on the user device.

8. The method of claim 1 , wherein loading a state further includes,

determining applications and/or processes that were executing prior to transfer; and

executing the applications and/or processes from the updated version, the execution causing the loading of the state of the applications and/or processes that were previously executing into the updated version of the application and/or processes currently executing.

9. An application updating system, comprising:

a processor; and

a memory disposed in communication with the processor and storing processor- executable instructions, the instructions comprising instructions to:

obtain an indication to check whether to generate an updated version of an application;

obtain a module dependency graph for a current version of the application;

identify current module version numbers for one or more modules in the module dependency graph for the current version of the application;

obtain, for the modules in the module dependency graph, module version numbers for updated module versions stored in a code database;

obtain compatibility specifications for the current version of the application and the updated module versions stored in the code database;

analyze the compatibility specifications for the current version of the application and the updated module versions;

determine that the updated version of the application can be generated using the updated module versions stored in the code database, based on analyzing the compatibility specifications for the current version of the application and the updated module versions and based on updates available within the updated module versions for the application; and

generate the updated version of the application using the updated module versions stored in the code database, the generation of the updated version causes transfer of a user from the current version of the application to the updated version of the application and dynamically establishes access for the user to the updated version, wherein the transfer of the user is performed in real-time while the user is utilizing the application, wherein dynamically establishing access includes loading a state associated with the user for the current version of the application prior to the transfer, into the updated version of the application.

10. The system of claim 9 , the instructions further comprising instructions to:

obtain an updated module version for one of the modules in the module dependency graph of the current version of the application; and

generate the updated version of the application using the obtained updated module version.

11. The system of claim 9 , wherein the instructions to identify the current module version numbers for the one or more modules in the module dependency graph for the current version of the application include instructions to:

obtain the current version of the application;

parse the obtained current version of the application; and

determine the module dependency graph of the current version of the application based on parsing the current version of the application.

12. The system of claim 9 , wherein the application is a multi-user social networking application.

13. The system of claim 9 , wherein the compatibility specifications include information on at least one of: hardware requirements; operating system requirements; and web browser requirements.

14. The system of claim 10 , the instructions further comprising instructions to:

provide a notification for a user of the generated updated version of the application;

obtain an indication to provide the updated version of the application for the user; and

provide the updated version of the application for the user.

15. The system of claim 14 , the instructions further comprising instructions to:

obtain an indication that the updated version of the application replaced the current version of the application on a user device as the user was using the application on the user device.

16. A processor-readable medium tangibly storing processor-executable application updating instructions, the instructions comprising instructions to:

obtain an indication to check whether to generate an updated version of an application;

obtain a module dependency graph for a current version of the application;

identify current module version numbers for one or more modules in the module dependency graph for the current version of the application;

obtain, for the modules in the module dependency graph, module version numbers for updated module versions stored in a code database;

obtain compatibility specifications for the current version of the application and the updated module versions stored in the code database;

analyze the compatibility specifications for the current version of the application and the updated module versions;

determine that the updated version of the application can be generated using the updated module versions stored in the code database, based on analyzing the compatibility specifications for the current version of the application and the updated module versions and based on updates available within the updated module versions for the application; and

generate the updated version of the application using the updated module versions stored in the code database, the generation of the updated version causes transfer of a user from the current version of the application to the updated version of the application and dynamically establishes access for the user to the updated version, wherein the transfer of the user is performed in real-time while the user is utilizing the application, wherein dynamically establishing access includes loading a state associated with the user for the current version of the application prior to the transfer, into the updated version of the application.

17. The system of claim 16 , the instructions further comprising instructions to:

obtain an updated module version for one of the modules in the module dependency graph of the current version of the application; and

generate the updated version of the application using the obtained updated module version.

18. The medium of claim 16 , wherein the instructions to identify the current module version numbers for the one or more modules in the module dependency graph for the current version of the application include instructions to:

obtain the current version of the application;

parse the obtained current version of the application; and

determine the module dependency graph of the current version of the application based on parsing the current version of the application.

19. The medium of claim 16 , wherein the application is a multi-user social networking application.

20. The medium of claim 16 , wherein the compatibility specifications include information on at least one of: hardware requirements; operating system requirements; and web browser requirements.

21. The medium of claim 17 , the instructions further comprising instructions to:

provide a notification for a user of the generated updated version of the application;

obtain an indication to provide the updated version of the application for the user; and

provide the updated version of the application for the user.

22. The medium of claim 21 , the instructions further comprising instructions to:

obtain an indication that the updated version of the application replaced the current version of the application on a user device as the user was using the application on the user device.

Assignments (5)
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded May 23, 2022
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: ZYNGA INC.
Reel/Frame 060163/0437 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Dec 14, 2020
From: ZYNGA INC.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 054719/0490 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 11, 2020
From: BANK OF AMERICA, N.A., AS LENDER
To: ZYNGA INC.
Reel/Frame 054701/0393 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Dec 21, 2018
From: ZYNGA INC.
To: BANK OF AMERICA, N.A., AS LENDER
Reel/Frame 049147/0546 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2011
From: MAHAJAN, AMITT; RAJLICH, LUKE
To: ZYNGA INC.
Reel/Frame 027024/0291 →