Web Service getting url and soap data - Design question

Hi

I'm currently updating an old (over 5 years) web Service (can't do much about the consumer side as that is fixated).

The Service has the following layout for one of its methods:

public string ServiceProc(string programName, string code, string requestcode, int datalength, short timeout)

Inside that method parts of the URL itself were decoded and include a user id and some other data (userId, nextUrl, Codepage).

Back then  WebService.Server.UrlDecode was used to decode the Url itself.

Now what I'm not so sure about is how it Looks These days. Do I still have to use those old design methods (and classes), or is there any way to use a more modern Approach like MVC 4 there?

(MVC I've seen for URL only things already, but in this case ist a bit of a mix between URL and Soap data Transfer, so I'm not sure if ist possible at all that way or not)