Basic Idea - You have one controller per page(or per view) on AngularJS side . A controller's job is to mix mash data from services to fit it to a view (controller can have a one to one relationship with a web view or web page)
AngularJS is MVC based , for each AngularJS Controller you may need one or more services and these can be virtual REST services - mapped to Spring MVC's view rendered JSON. Spring MVC View would have a one on one relationship with a controller for neatness sake .
So each of the corresponding controllers on server side in Spring MVC , would call one or more than one Java Service classes which might fetch data from RESTful APIs.
One can structure the application in the below manner:
Angular JS View has one to one relationship with Angular JS Controller
Angular JS Controller has one to many relationship with AngularJS service
AngularJS Service has one to one relationship with Spring MVC View and so does it with Spring MVC Controller
Spring MVC Controller can have one to many relationship with Spring Model (Service) classes