How does the MVC Archiver + Service layer work?

In this case, the service layer is interpreted as part of the MVC (model-view-controller) architecture and not as something additional.

The view shows the user the interface and options he will have, so by selecting something, the controller decides how the service will handle and calls the model to meet the user's request.

If the service is something internal and you can include it in the controller and / or model, it is the right place. If the service is external, your controller will probably access it as if it were a model, even if part of the logic is done by the service.

For example, if you have SoA software, it typically does not include the Vision part. To integrate SoA software with an MVC, MVC is likely to use SoA as a template.