'Back' button in mobile applications

• US 20050114798A1
• Filed: 06/14/2004
• Published: 05/26/2005
• Est. Priority Date: 11/10/2003
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Oath Inc. (Verizon Communications Inc.)
• Inventors: Sato, Joy, Cui, Yingqing Lawrence, Wu, Christopher, Jiang, Zhaowei Charlie
• Application Number:
  US10/868,416
• Publication Number:
  US 20050114798A1
• Time in Patent Office: Days
• US Class Current: 715/864
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A wireless system includes a plurality of mobile devices equipped with a touch-activated ‘back’ command input, button or soft key, that prompts backwards navigation. The system further includes a carrier network, a network including at least the Internet, and a server. The plurality of mobile devices are interconnected with the server via the carrier network and the network and are capable of communicating with each other via the server. One or more than one mobile devices has a touch-activated ‘back’ command input and a memory with sufficient space for receiving a mobile client application from the server, wherein the mobile client application is responsive to the touch-activated ‘back’ command input by providing the backwards navigation through screens in ‘back in sequence’ mode or ‘back a level’ mode.

Claims

1. A method for backwards navigation on a mobile device with a touch-activated command input and a state stack, comprising:

providing, while in a current state, a ‘

back’

command from the touch activated command input;

popping out a state from the state stack in response to the ‘

back’

command, the popped out state replacing the current state as the new current state;

generating a run-time environment in the mobile device for the new current state; and

displaying a screen associated with the new current state along with a user interface to other states.

2. A mobile device as in claim 1, wherein the touch-activated ‘

back’

command input includes a button or a soft key.

3. A method as in claim 1, wherein the backwards navigation is conducted either in a back in sequence mode or in a back a level mode.

4. A method as recited in claim 3 where, in the back in sequence mode, the popped out state is a last-in state removed from the top of the state stack.

5. A method as in claim 3 where, in the back a level mode, the popped out state is a parent state removed from the top of the state stack.

6. A method as in claim 3 where, in the back in sequence mode, the state stack holds a sequential state path that records a sequential forward flow through each state up to the current state.

7. A method as in claim 6, further comprising, in the back in sequence mode, recording the forward flow in a state history stack for future restoration of user interactions.

8. A method as in claim 3 where, in the back a level mode, the state stack holds a hierarchical state path, recording parent states in a forward flow up to the current state, such that the backwards navigation follows, in reverse, the hierarchical state path.

9. A method as in claim 1, wherein the run-time environment in the mobile device is provided for a client mobile photos application resident in the mobile device and responsive to the touch-activated ‘

back’

command input.

10. A method as in claim 9, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with a mobile album of photos.

11. A method as in claim 9, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with an online album of photos.

12. A mobile device with a touch-activated ‘

back’

command, comprising;

a touch-activated ‘

back’

command input;

means for providing, while in a current state, a ‘

back’

command from the touch activated ‘

back’

command input;

a data structure for holding states;

means for popping out a state from the data structure in response to the ‘

back’

command, the popped out state replacing the current state as the new current state;

means for generating a run-time environment in the mobile device for the new current state; and

means for displaying a screen associated with the new current state along with a user interface to other states.

13. A mobile device as in claim 12, wherein the ‘

back’

command is associated with backwards navigation which is conducted on the mobile device either in a back in sequence mode or in a back a level mode.

14. A mobile device as recited in claim 13, wherein the data structure is a state stack, and where, in the back in sequence mode, the popped out state is a last-in state removed from the top of the state stack.

15. A mobile device as in claim 13, wherein the data structure is a state stack, and where, in the back a level mode, the popped out state is a parent state removed from the top of the state stack.

16. A mobile device as in claim 13 where, in the back in sequence mode, the data structure holds a sequential state path that records a sequential forward flow through each state up to the current state.

17. A mobile device as in claim 16, further comprising a state path data structure configured to hold the forward flow in the back in sequence mode.

18. A mobile device as in claim 13 where, in the back a level mode, the data structure holds a hierarchical state path, recording parent states in a forward flow up to the current state, such that the backwards navigation follows, in reverse, the hierarchical state path.

19. A mobile device as in claim 12, wherein the run-time environment in the mobile device is provided for a client mobile photos application resident in the mobile device and responsive to the touch-activated ‘

back’

command input, the client program being dynamically loadable to the mobile device on demand from a server via the Internet and a bearer network.

20. A mobile device as in claim 19, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with a mobile album of photos.

21. A mobile device as in claim 19, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with an online album of photos.

22. A mobile device as in claim 12, configured as a wireless, mobile camera phone capable of capturing images and uploading the captured images to a server via a bearer network and the internet.

23. A mobile device as in claim 12, configured as a wireless mobile device capable of dynamically pulling data form a server and pushing data to the server, via the wireless network and the Internet.

24. A mobile device as in claim 12, configured as a wireless application protocol-compliant device.

25. A mobile computer system embodying a touch-activated ‘

back’

command input, a data structure for holding states, and program code for backwards navigation responsive to ‘

back’

commands comprising;

program code for responding, while in a current state, to a ‘

back’

command from the touch activated ‘

back’

command input;

program code for popping out a state from the data structure in response to the ‘

back’

command, the popped out state replacing the current state as the new current state;

program code for generating a run-time environment in the mobile device for the new current state; and

program code for displaying a screen associated with the new current state along with a user interface to other states.

26. A mobile device as in claim 25, wherein the ‘

back’

command is associated with backwards navigation which is conducted on the mobile device either in a back in sequence mode or in a back a level mode.

27. A mobile device as recited in claim 26, wherein the data structure is a state stack, and where, in the back in sequence mode, the popped out state is a last-in state removed from the top of the state stack.

28. A mobile device as in claim 26, wherein the data structure is a state stack, and where, in the back a level mode, the popped out state is a parent state removed from the top of the state stack.

29. A mobile device as in claim 26 where, in the back in sequence mode, the data structure holds a sequential state path that records a sequential forward flow through each state up to the current state.

30. A mobile device as in claim 29, further comprising a state path data structure configured to hold the forward flow in the back in sequence mode.

31. A mobile device as in claim 26 where, in the back a level mode, the data structure holds a hierarchical state path, recording parent states in a forward flow up to the current state, such that the backwards navigation follows, in reverse, the hierarchical state path.

32. A mobile device as in claim 25, wherein the run-time environment in the mobile device is provided for a client mobile photos application resident in the mobile device and responsive to the touch-activated ‘

back’

command input, the client program being dynamically loadable to the mobile device on demand from a server via the Internet and a bearer network.

33. A mobile device as in claim 32, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with a mobile album of photos.

34. A mobile device as in claim 32, wherein the client mobile photos application provides for forward and backwards navigation through states corresponding to screens associated with an online album of photos.

35. A mobile device as in claim 25, configured as a wireless, mobile camera phone capable of capturing images and with further program code for uploading the captured images to a server via a bearer network and the internet.

36. A mobile device as in claim 25, configured as a wireless mobile device capable of dynamically pulling data form a server and pushing data to the server, via the wireless network and the Internet.

37. A mobile device as in claim 25, configured with program code for operating as a wireless application protocol-compliant device.

38. A mobile device with a touch activated ‘

back’

command, comprising;

a touch-activated ‘

back’

command input;

a touch-activated ‘

menu’

command input; and

a memory with sufficient space for storing a mobile client application, wherein the mobile device is responsive to the touch-activated ‘

menu’

command input for activating the mobile client application which is, in turn, responsive to the touch activated ‘

back’

command input by providing backwards navigation through screens in ‘

back in sequence’

mode or ‘

back a level’

mode.

39. A mobile device as in claim 38, further comprising:

a display configured with sufficient resolution for text and graphic display, including display of a menu screen associated with the touch-activated ‘

menu’

command input; and

a touch-activated selection command input for selecting a menu item from the menu screen or an action or menu item from another screen.

40. A mobile device as in claim 39, wherein the touch-activated ‘

menu’

command and selection command inputs are configured to allow forward flow of screens.

41. A mobile device as in claim 40, further comprising a state stack configured to record the forward flow either sequentially or hierarchically, thereby facilitating the backwards navigation.

42. A mobile device as in claim 40, further comprising a state history stack configured to record the forward flow for future restoration of user interaction.

43. A mobile device as in claim 39, configured as a wireless, mobile camera phone capable of capturing images and uploading the captured images to a server via a bearer network and the internet.

44. A mobile device as in claim 38, configured for operating as a wireless application protocol-compliant device.

45. A mobile device as in claim 38 with functionality and profile implemented using a Java 2 Micro Edition (J2ME™

) platform.

46. A mobile device as in claim 38, wherein the touch-activated ‘

back’

command input includes a button or a soft key.

47. A wireless system with mobile devices equipped with a touch-activated ‘

back’

command input, comprising;

a carrier network;

a network including at least the Internet;

a server;

a plurality of mobile devices interconnected with the server via the carrier network and the network and being capable of communicating with each other via the server, one or more than one mobile device having a touch-activated ‘

back’

command input and a memory with sufficient space for receiving a mobile client application from the server, wherein the mobile client application is responsive to the touch-activated ‘

back’

command input by providing backwards navigation through screens in ‘

back in sequence’

mode or ‘

back a level’

mode.

48. A wireless system as in claim 47, further comprising a carrier gateway disposed between the carrier network and the network for tracking subscriber activities and controlling their data communications, as well as, for functioning as a proxy for the mobile devices, on one hand, and for the server, on the other hand.

49. A wireless system as in claim 47, wherein the one or more than one mobile device with the touch-activated ‘

back’

command input and memory for receiving the mobile client application, further has a touch-activated ‘

menu’

command input, wherein the mobile device is responsive to the touch-activated ‘

menu’

command input for activating the mobile client application.

50. A wireless system as in claim 49, in which the one of more than one mobile device with the touch-activated ‘

back’

command input, the touch-activated ‘

menu’

command input, and the memory for receiving the mobile client application, further includes;

a display configured with sufficient resolution for text and graphic display, including display of a menu screen associated with the touch-activated ‘

menu’

command input; and

a touch-activated selection command input for selecting a menu item from the menu screen or an action or menu item from another screen.

51. A wireless system as in claim 50, wherein the touch-activated ‘

menu’

command and selection command inputs are configured to allow forward flow of screens.

52. A wireless system as in claim 51, in which the one of more than one mobile device that includes the touch-activated ‘

back’

command input, the touch-activated ‘

menu’

command input, and the memory for receiving the mobile client application, further includes a state stack configured to record the forward flow either sequentially or hierarchically, thereby facilitating the backwards navigation.

53. A mobile device as in claim 51, in which the one of more than one mobile device with the touch-activated ‘

back’

command input, the touch-activated ‘

menu’

command input, and the memory for receiving the mobile client application, further includes a state history stack configured to record the forward flow for future restoration of user interaction.

54. A mobile device as in claim 50, in which the one of more than one mobile device with the touch-activated ‘

back’

command input, the touch-activated ‘

menu’

command input, and the memory for receiving the mobile client application, is configured as a wireless, mobile camera phone capable of capturing images and uploading the captured images to the server via network and the carrier network.

55. A mobile device as in claim 47, wherein the touch-activated ‘

back’

command input includes a button or a soft key.