COLLABORATIVE APPLICATION DEVELOPMENT ENVIRONMENT USING A CONNECTED DEVICE

• US 20140258970A1
• Filed: 03/11/2013
• Published: 09/11/2014
• Est. Priority Date: 03/11/2013
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Brown, Michael Stephen, Dent, Terrill Mark, Kalu, Kalu Onuka
• Granted Patent: US 9,158,518 B2
• Time in Patent Office: Days
• US Class Current: 717/103
• CPC Class Codes: G06F 8/47 Retargetable compilers
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

The present disclosure provides a Web-based integrated development environment and graphical user interface for real-time collaborative application development which uses a connected device. Changes made to an application within the application development tool are applied to a connected mobile device in real-time or near real-time application.

Claims

1. A method of synchronizing an application between a client computer to a mobile device, the method comprising:

receiving a request from a client computer to publish an application associated with an application identifier ApplicationID at a first application state to a mobile device, wherein the request includes a user identifier UserID associated with a current user of the client computer and an IP address of the mobile device TargetIPAddress;

compiling the application in accordance with application code defining the application at a save point prior to the first application state;

sending the compiled application to the mobile device at the IP address TargetIPAddress along with identifying information comprising an IP address of the server.

2. The method of claim 1, further comprising:

receiving an authorization request from the mobile device, the authorization request including identifying information comprising the application identifier ApplicationID, the user identifier UserID and a device identifier DeviceID associated with the mobile device;

sending a device authorization request to the client computer when the combination of the application identifier ApplicationID, user identifier UserID and device identifier DeviceID do not correspond to any previously authorized mobile devices;

generating a token defining an association between the application identifier ApplicationID, the user identifier UserID and the device identifier DeviceID in response to receiving a device authorization message from the client computer; and

sending the token to the mobile device associated with the device identifier DeviceID at the IP address TargetIPAddress.

3. The method of claim 2, further comprising:

denying the authorization request in response to receiving a device denial message from the client computer.

4. The method of claim 1, further comprising:

receiving an authorization request from the mobile device, the authorization request including identifying information comprising the application identifier ApplicationID, the user identifier UserID and a device identifier DeviceID associated with the mobile device;

generating a token defining an association between the application identifier ApplicationID, the user identifier UserID and the device identifier DeviceID in response to the receiving the authorization request; and

sending the token to the mobile device associated with the device identifier DeviceID at the IP address TargetIPAddress.

5. The method of claim 4, further comprising:

sending identifying information about the mobile device associated with the device identifier. DeviceID to the client computer.

6. The method of claim 2, further comprising:

sending to the mobile device associated with the device identifier DeviceID at the IP address TargetIPAddress any incremental changes to the application code which occurred between the save point and the first application state.

7. The method of claim 6, further comprising:

receiving a request from the mobile device associated with the device identifier DeviceID, wherein the request requests any subsequent change to the application made to the application by the user associated with the user identifier UserID, wherein the request is associated with the token.

8. The method of claim 7, further comprising:

receiving from the client computer a change request including change information describing one or more change(s) to the application, wherein the change request is associated with the user identifier UserID; and

sending the change request to the mobile device associated with the device identifier DeviceID at the IP address TargetIPAddress when an open request requesting any subsequent change to the application made to the application by the user associated with the user identifier UserID exists for the mobile device.

9. The method of claim 8, wherein the change request changes a current state of the application on the client computer associated with the user identifier UserID from the first application state to another application state.

10. The method of claim 8, wherein the change request changes an active page of the application displayed on the client computer associated with the user identifier UserID.

11. The method of claim 8, wherein the change request adds, deletes or modifies an object in the active page of the application displayed on the client computer associated with the user identifier UserID.

12. The method of claim 7, further comprising:

receiving from the mobile device associated with the device identifier DeviceID a change request including change information describing one or more change(s), wherein the change request is associated with the user identifier UserID;

sending the change request to the client computer associated with the user identifier UserID.

13. The method of claim 12, wherein the change request is sent to the client computer at an IP address UserIPAddress.

14. The method of claim 13, wherein the one or more change(s) information comprises one or more of a change in device state or a change to the application.

15. The method of claim 6, further comprising:

receiving a request from the mobile device associated with the device identifier DeviceID requesting any subsequent change to the application made to the application by the user associated with the user identifier UserID;

rejecting the request when not associated with the valid token;

accepting the request when associated with the token.

16. The method of claim 6, further comprising:

receiving a request from the client computer associated with the user identifier UserID to acquire sensor data from the mobile device associated with the device identifier DeviceID;

sending an instruction to acquire the sensor data to the mobile device associated with the device identifier DeviceID at the IP address TargetIPAddress;

receiving the sensor data from the mobile device associated with the device identifier DeviceID; and

sending the sensor data to the client computer associated with the user identifier UserID.

17. The method of claim 16, further comprising storing the sensor data in memory.

18. The method of claim 17, wherein the sensor data is stored as an incremental change, wherein the method further comprises sending the sensor data to all collaborating devices currently accessing the application associated with the application identifier ApplicationID.

19. The method of claim 14, wherein the sensor data comprises an image captured by a camera of the mobile device associated with the device identifier DeviceID.

20. The method of claim 1, wherein the save point is the most recent save point.

21. A method for synchronizing changes between an application between a client computer and a mobile device, the method comprising:

receiving from the client computer first change information describing an incremental change to the application, wherein the first change information is associated with a user identifier UserID associated with a current user of the client computer;

receiving from a client computer a first change request including first change information describing one or more change(s) to the application, wherein the first change request is associated with a user identifier UserID associated with a current user of the client computer; and

storing the first change request in memory in association with the user identifier UserID; and

sending the first change request to a mobile device associated with the device identifier DeviceID and the user identifier UserID.

22. The method of claim 21, further comprising:

receiving from the mobile device associated with the device identifier DeviceID a second change request including second change information describing one or more change(s), wherein the second change request is associated with the user identifier UserID;

storing the second change request in memory in association with the user identifier UserID; and

sending the second change request to the client computer associated with the user identifier UserID.

23. The method of claim 22, wherein the second change request includes second change information describing one or more of a change in device state or a change to the application.

24. A method for synchronizing changes between an application between a client computer and a mobile device, the method comprising:

receiving from a mobile device associated with the device identifier DeviceID a second change request including second change information describing one or more change(s), wherein the second change request is associated with a user identifier UserID;

storing the second change request in memory in association with the user identifier UserID; and

sending the second change request to a client computer associated with the user identifier UserID.

25. A method for acquiring sensor data from a mobile device, the method comprising:

receiving a request from a client computer associated with a user identifier UserID to acquire sensor data from a mobile device associated with a device identifier DeviceID;

sending an instruction to acquire the sensor data to the mobile device associated with the device identifier DeviceID at an IP address TargetIPAddress;

receiving the sensor data from the mobile device associated with the device identifier DeviceID; and

sending the sensor data to the client computer associated with the user identifier UserID.