Design pattern

I think you're expecting a little too much out of design patterns. They exist to handle generic code organisation concepts that software often encounters, rather than specific real world use cases such as networking.

The Proxy pattern may be useful for treating remote objects as if they're local, effectively abstracting the communication aspect away from the interface of an object.

But in general Kylotan is dead right, they're design patterns, not design solutions.

Some of these are applicable.