This is not so much an advantage as an axiom - the segmentation model 8086 of the real mode is designed at the hardware level, so the segment register determines the border of the paragraph.
The segment register set the base address of the upper 16 bits of the 8086-bit address space 8086, the lower 4 bits of this base address were essentially forced to zero.
Segmented architecture was one way that the 1686-bit register architecture could address the full megabyte (!) Of the address space (which requires 20 bits of addressing).
For a bit more history, the next step Intel took in the x86 architecture was to abstract segment registers from directly defining the base address. This was protected mode 286, in which the segment register held a “selector”, which, instead of defining bits for the physical base address, was an index into a set of descriptor tables containing information about the physical address, permissions to access the physical memory address, etc.
Segment registers in modern 32-bit or larger x86 processors still do this. But when address offsets can indicate full 32-bit addressing (or 64-bit on x64 processors) and page tables capable of providing semantics of virtual memory in a segment defined by a selector, the programming model essentially eliminates the need to manipulate segment registers at the application level. For the most part, the OS sets up the segment registers once, and nothing else they need to solve. Therefore, programmers usually do not even need to know that they exist.
source share