Can AngularJS route a user to the same instance of the same view in memory?

I have an AngularJS 1.6 app. There is one particular route to a view that displays a calendar to the user.

When the user clicks on entries in the calendar, they are routed to a view with information about that entry. Before the user is routed away from the calendar view, the state of the calendar is saved in an AngularJS service so that when the user eventually returns to the calendar view, the state can be retrieved from the AngularJS service and used to initialize the calendar to a similar state.

The above is a working solution.

However, I would like to know if AngularJS has functionality so that when the user is routed to another view from the calendar, the calendar view can somehow stay resident in memory so that when the user returns to the calendar view, the user can be presented with the same calendar view instead of having to initialize a new instance of the calendar view.