Broker Vs Gateway pattern

I'm a bit confused about those two - Broker and Gateway EAA patterns. It seems that Broker can:

structure distributed software systems with decoupled components that interact by remote service invocations

and Gateway

Wrap all the special API code into a class whose interface looks like a regular object. Other objects access the resource through this Gateway, which translates the simple method calls into the appropriate specialized API.

If so - how they differ?